Geoffrey Keating wrote:
> BIGGEST_ALIGNMENT is 128 for a number of reasons, but
> PREFERRED_STACK_BOUNDARY is 128 primarily so that code compiled with
> -meabi can also be used on Linux and other SVR4 targets, and for
> Altivec support.
I see. Both would deserve comments, IMHO.
Thanks for your
Olivier Hainque <[EMAIL PROTECTED]> writes:
> Hello,
>
> PPC EABI targets are currently configured with both BIGGEST_ALIGNMENT and
> PREFERRED_STACK_BOUNDARY set to 128, I believe to accomodate
>
> "a long double member within a structure or union shall start at the lowest
>available offse
Dave Korn wrote:
> > "a long double member within a structure or union shall start at the
> >lowest available offset aligned on a 16byte boundary"
> It only implies that the offset should be such a multiple, but since the
> struct itself will have to be aligned to a multiple of 16 if any o
Original Message
>From: Olivier Hainque
>Sent: 26 April 2005 14:25
> "a long double member within a structure or union shall start at the
>lowest available offset aligned on a 16byte boundary"
>
> Now, I'm a bit unclear on the meaning of the ABI statement quoted above,
> and on the
Hello,
PPC EABI targets are currently configured with both BIGGEST_ALIGNMENT and
PREFERRED_STACK_BOUNDARY set to 128, I believe to accomodate
"a long double member within a structure or union shall start at the lowest
available offset aligned on a 16byte boundary"
Besides, for 32bit non-alt
