Displaying 4 results from an estimated 4 matches for "sretreturnreg".
2012 Sep 04
0
[LLVMdev] Lowering Call Return
On 9/4/2012 11:16 AM, Khaled Mohammed wrote:
>
> Is there an option to do sret demotion via a register? if yes, do we
> have a Target to see an example implementation?
Hi Khaled,
Check out X86TargetLowering::LowerReturn, and the call to getSRetReturnReg.
The SRetReturnReg looks like a hack (each target that uses it, declares
this variable individually), but that seems to be the current way of
handling it.
-K
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
2012 Sep 04
2
[LLVMdev] Lowering Call Return
Hi,
it seems like SelectionDAGBuilder expects returning of vectors
(structures/arrays) to be lowered in either of the two ways:
1. Flatten the complex data types to simple data types, and return them
using registers (done by TargetLowering::LowerCallTo)
2. sret demotion: return the address of the complex data type via a stack
pointer
Is there an option to do sret demotion via a register? if yes,
2012 Sep 05
2
[LLVMdev] Lowering Call Return
...9/4/2012 11:16 AM, Khaled Mohammed wrote:
>
>>
>> Is there an option to do sret demotion via a register? if yes, do we
>> have a Target to see an example implementation?
>>
>
> Hi Khaled,
>
> Check out X86TargetLowering::**LowerReturn, and the call to
> getSRetReturnReg.
>
> The SRetReturnReg looks like a hack (each target that uses it, declares
> this variable individually), but that seems to be the current way of
> handling it.
>
> -K
>
> --
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted
> by The Linux F...
2012 Dec 03
1
[LLVMdev] operator overloading fails while debugging with gdb for i386
On 3 December 2012 10:42, Mayur Pandey <mayurthebond at gmail.com> wrote:
> So this seems to be the cause of the problem.
I guess you're mixing two different problems. First, is the possible
lack of conformance with the ABI you state, which I can't comment
since I don't know that ABI very well. Second, is the fact that clang
is not printing correct debug information (or is