register (like clang )or memory
to return not the SSE registers.
Before we go ahead and fix this issue and we would like to know the
community views/comments on the same.
--
Thanks & Regards
Lokesh Janghel
.
--
Thanks & Regards
Lokesh Janghel
Hi Sirl,
As you mention in Bugzilla (comment 13),
aix_return( return in memory)
svr4_return(in registers)
what is the semantics of *svr4gnu* w.r.t return .
On Mon, Nov 19, 2018 at 11:33 PM Franz Sirl <
franz.sirl-ker...@lauterbach.com> wrote:
> Am 2018-11-19 um 15:36 schrieb Lokes
roduce this issue.
>
> Hi,
>
> you already reproduced the issue, according to the ABI, the code should
> look like:
>
> .LFB0:
> stwu 1,-32(1)
> .LCFI0:
> lis 3,0x1122
> ori 3,3,0x3300
> addi 1,1,32
> .LCFI1:
> blr
>
> So the value being passed around should be left-aligned in the register.
>
> > Sirl,
> > If you got the patch for this issue or will look into the issue.
>
> I have an unfinished patch, it misses commandline handling, testcases
> and some code comments. I've attached it.
>
> It's unlikely I can continue to work on it anytime soon :-(.
>
> Franz
>
--
Thanks & Regards
Lokesh Janghel
+91-9752984749
Hi Sirl,
As you mentioned in Bugzilla (comment 13),
aix_return ( return in memory)
svr4_return (return in register)
what is the semantics of svr4gnu w.r.t. return.
Thanks
Lokesh
Hi Sirl,
As you mentioned in Bugzilla (comment 13),
aix_return ( return in memory)
svr4_return (return in register)
what is the semantics of svr4gnu w.r.t. return.
On Mon, Nov 19, 2018 at 11:33 PM Franz Sirl
wrote:
>
> Am 2018-11-19 um 15:36 schrieb Lokesh Janghel:
> > Hi Segher,
Thank you Sirl,
>>-msvr4-struct-return=standard and -msvr4-struct-return=gnu (which would
be the default (-msvr4-struct-return=standard)
by default, you mean using registers to return?
Lokesh
On Fri, Nov 30, 2018 at 4:18 PM Franz Sirl
wrote:
>
> Am 2018-11-26 um 06:13 schrieb Lo
Hi,
As per our analysis on the issue, I have some queries as per below:
Is there any target hooks for alloca?
Should we do the same like __builtin_alloca_with_align (array
allocation) or we assume the problem as a target based
(prologue/epilogue optimization) issue?
--
Thanks
Lokesh