search for: ccaction

...a new entity that tells the calling convention > code to to let the target do something not easily representable > in the tablegen minilanguage. I am thinking that this requires two changes: add a flag to CCValAssign (take a bit from HTP) to indicate isCustom and a way to author an arbitrary CCAction by including the source directly in the TableGen mini-language. This latter change might want a generic change to the TableGen language. For example, the syntax might be like: class foo : CCCustomAction { code <<< EOF ....multi-line C++ code goes here that allocates regs & mem a...

...calling convention >> code to to let the target do something not easily representable >> in the tablegen minilanguage. > > I am thinking that this requires two changes: add a flag to > CCValAssign (take a bit from HTP) to indicate isCustom and a way to > author an arbitrary CCAction by including the source directly in the > TableGen mini-language. This latter change might want a generic change > to the TableGen language. For example, the syntax might be like: > > class foo : CCCustomAction { > code <<< EOF > ....multi-line C++ code goes here tha...

...>> code to to let the target do something not easily representable >>> in the tablegen minilanguage. >> >> I am thinking that this requires two changes: add a flag to >> CCValAssign (take a bit from HTP) to indicate isCustom and a way to >> author an arbitrary CCAction by including the source directly in the >> TableGen mini-language. This latter change might want a generic change >> to the TableGen language. For example, the syntax might be like: >> >> class foo : CCCustomAction { >> code <<< EOF >> ....multi-lin...

...Also, moving the option there will allow us to change fastcc ABI (callee popping arguments) only when this option is on. See Chris' email: > Sure it can be, you can set up custom predicates, for example the > X86CallingConv.td file has: > > class CCIfSubtarget<string F, CCAction A> > : CCIf<! strconcat("State.getTarget().getSubtarget<X86Subtarget>().", F), A>; > > It would be straight-forward to have a CCIf defined to check some command > line argument. +/// IsEligibleForTailCallElimination - Check to see whether the next ins...

...> >> Hmmm. Ok. So this is due to X86CallingConv.td changes? Unfortunately >> that's not controlled by options. Ok then. >> > > Sure it can be, you can set up custom predicates, for example the > X86CallingConv.td file has: > > class CCIfSubtarget<string F, CCAction A> > : CCIf<!strconcat("State.getTarget().getSubtarget<X86Subtarget> > ().", F), A>; > > It would be straight-forward to have a CCIf defined to check some > command > line argument. I think enabling this as llcbeta for a few nights > makes >...

...let the target do something not easily representable >>>> in the tablegen minilanguage. >>> >>> I am thinking that this requires two changes: add a flag to >>> CCValAssign (take a bit from HTP) to indicate isCustom and a way to >>> author an arbitrary CCAction by including the source directly in the >>> TableGen mini-language. This latter change might want a generic >>> change >>> to the TableGen language. For example, the syntax might be like: >>> >>> class foo : CCCustomAction { >>> code <<&...

...mething not easily representable >>>>> in the tablegen minilanguage. >>>> >>>> I am thinking that this requires two changes: add a flag to >>>> CCValAssign (take a bit from HTP) to indicate isCustom and a way to >>>> author an arbitrary CCAction by including the source directly in the >>>> TableGen mini-language. This latter change might want a generic >>>> change >>>> to the TableGen language. For example, the syntax might be like: >>>> >>>> class foo : CCCustomAction { >>&...

...ts in GCC). For calling conventions compatible with Turbo/Pure C the first two pointes would also go in a0-a1, and the first three integers in d0-d2 (This is not supported by official GCC as of now). Simply subclassing CCIf and check ValVT or LocVT like this does not work: class CCIfPointer<CCAction A> : CCIf<"LocVT==MVT::iPTR", A> { } Do I have to extend ISD::ArgFlagsTy with a "IsPtr" flag that is populated, maybe in SelectionDAGISel::LowerCallTo and ::LowerArguments? Or is there a better and more obvious way? // Fredrik

...t; call optimization in a general way. > > Hmmm. Ok. So this is due to X86CallingConv.td changes? Unfortunately > that's not controlled by options. Ok then. Sure it can be, you can set up custom predicates, for example the X86CallingConv.td file has: class CCIfSubtarget<string F, CCAction A> : CCIf<!strconcat("State.getTarget().getSubtarget<X86Subtarget>().", F), A>; It would be straight-forward to have a CCIf defined to check some command line argument. I think enabling this as llcbeta for a few nights makes sense before turning it on by default. -Ch...

...t;>>> in the tablegen minilanguage. >>>>> >>>>> I am thinking that this requires two changes: add a flag to >>>>> CCValAssign (take a bit from HTP) to indicate isCustom and a way >>>>> to >>>>> author an arbitrary CCAction by including the source directly in >>>>> the >>>>> TableGen mini-language. This latter change might want a generic >>>>> change >>>>> to the TableGen language. For example, the syntax might be like: >>>>> >>>>...

...the tablegen minilanguage. >>>>>> >>>>>> I am thinking that this requires two changes: add a flag to >>>>>> CCValAssign (take a bit from HTP) to indicate isCustom and a way >>>>>> to >>>>>> author an arbitrary CCAction by including the source directly in >>>>>> the >>>>>> TableGen mini-language. This latter change might want a generic >>>>>> change >>>>>> to the TableGen language. For example, the syntax might be like: >>>>>&gt...

...gt;>>>> >>>>>>>> I am thinking that this requires two changes: add a flag to >>>>>>>> CCValAssign (take a bit from HTP) to indicate isCustom and a way >>>>>>>> to >>>>>>>> author an arbitrary CCAction by including the source directly in >>>>>>>> the >>>>>>>> TableGen mini-language. This latter change might want a generic >>>>>>>> change >>>>>>>> to the TableGen language. For example, the syntax might...

...his is due to X86CallingConv.td changes? Unfortunately >>> that's not controlled by options. Ok then. >>> >> >> Sure it can be, you can set up custom predicates, for example the >> X86CallingConv.td file has: >> >> class CCIfSubtarget<string F, CCAction A> >> : CCIf<!strconcat("State.getTarget().getSubtarget<X86Subtarget> >> ().", F), A>; >> >> It would be straight-forward to have a CCIf defined to check some >> command >> line argument. I think enabling this as llcbeta for a few nigh...

...guage. >>>>>>> >>>>>>> I am thinking that this requires two changes: add a flag to >>>>>>> CCValAssign (take a bit from HTP) to indicate isCustom and a way >>>>>>> to >>>>>>> author an arbitrary CCAction by including the source directly in >>>>>>> the >>>>>>> TableGen mini-language. This latter change might want a generic >>>>>>> change >>>>>>> to the TableGen language. For example, the syntax might be like: >&gt...

On Dec 27, 2008, at 4:30 AM, Sandeep Patel wrote: > Attached is a prototype patch that uses CCState to lower RET nodes in > the ARM target. Lowering CALL nodes will come later. > > This patch does not handle f64 and i64 types. For these types, it > would be ideal to request the conversions below: i64 isn't Legal on ARM, so it should already be handled. > > > def

On Sep 25, 2007, at 12:01 AM, Arnold Schwaighofer wrote: >>> FastCC use to be caller pops arguments so there was no stack >>> adjustment after the >>> call to qux. Now FastCC has callee pops arguments on return >>> semantics >>> so the >>> x86 backend inserts a stack adjustment after the call. >>> >>> _array: >>>

...>>> Unfortunately >>>> that's not controlled by options. Ok then. >>>> >>> >>> Sure it can be, you can set up custom predicates, for example the >>> X86CallingConv.td file has: >>> >>> class CCIfSubtarget<string F, CCAction A> >>> : CCIf<!strconcat("State.getTarget().getSubtarget<X86Subtarget> >>> ().", F), A>; >>> >>> It would be straight-forward to have a CCIf defined to check some >>> command >>> line argument. I think enabling this a...

...g that this requires two changes: add a flag to >>>>>>>>>> CCValAssign (take a bit from HTP) to indicate isCustom and a >>>>>>>>>> way >>>>>>>>>> to >>>>>>>>>> author an arbitrary CCAction by including the source >>>>>>>>>> directly in >>>>>>>>>> the >>>>>>>>>> TableGen mini-language. This latter change might want a >>>>>>>>>> generic >>>>>>>&gt...

...; I am thinking that this requires two changes: add a flag to >>>>>>>>> CCValAssign (take a bit from HTP) to indicate isCustom and a >>>>>>>>> way >>>>>>>>> to >>>>>>>>> author an arbitrary CCAction by including the source >>>>>>>>> directly in >>>>>>>>> the >>>>>>>>> TableGen mini-language. This latter change might want a >>>>>>>>> generic >>>>>>>>> change...

...;>>> CCValAssign (take a bit from HTP) to indicate isCustom >>>>>>>>>>>> and a >>>>>>>>>>>> way >>>>>>>>>>>> to >>>>>>>>>>>> author an arbitrary CCAction by including the source >>>>>>>>>>>> directly in >>>>>>>>>>>> the >>>>>>>>>>>> TableGen mini-language. This latter change might want a >>>>>>>>>>>> generic...