Displaying 3 results from an estimated 3 matches for "loweraguments".
Did you mean:
lowerarguments
2007 Oct 01
1
[LLVMdev] Q about instruction pattern matching
...the instruction selections later on?
> If not, how do I distinguish these arguments from the data argument
> later on?
Hrm. I suspect you'll have to add parameter attribute (see
ParameterAttributes.h) that indicates it's used as an address. In
SelectionDAGIsel.cpp:TargetLowering::LowerAguments(), you have access
to the function argument type. Anyone sees an alternative solution?
Evan
>
> Thanks,
> Andreas
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc...
2007 Oct 01
0
[LLVMdev] Q about instruction pattern matching
On 10/1/07, Evan Cheng <evan.cheng at apple.com> wrote:
> > If I lower the calling convention stuff manually rather than relying
> > on the generated CC analyzer, how do I determine that a formal
> > argument I'm about to receive or pack together is supposed to be used
> > as a pointer so I can stick it in an address register?
>
> I'd suggest custom
2007 Sep 30
2
[LLVMdev] Q about instruction pattern matching
On Sep 29, 2007, at 2:57 PM, Andreas Fredriksson
<deplinenoise at gmail.com> wrote:
> On 9/25/07, Evan Cheng <evan.cheng at apple.com> wrote:
>>> Hi Evan,
>>> wouldn't this generate fairly terrible code if each address register
>>> use has to be preceded by instructions to make an address register
>>> hold the right value?
>>
>>