because it was set before 2003. There could not be an ABI break.
r0-50273-gded9bf77e35ce9a2246 fixed GCC for the AIX ABI though.
>
> ~Umesh
>
> On Tue, Jun 6, 2023 at 8:28 PM Andrew Pinski wrote:
> >
> > On Tue, Jun 6, 2023 at 7:50 AM Umesh Kalappa via Libc-alpha
> &g
Plus the 32bit ABI document does not document Complex argument passing
as it was written in 1995 and never updated.
https://www.nxp.com/docs/en/reference-manual/E500ABIUG.pdf does not
document it either.
Thanks,
Andrew Pinski
>
> Page 53:
>
> Map complex floating-point and complex int
On Feb 18, 2008 6:01 AM, Geert Uytterhoeven
<[EMAIL PROTECTED]> wrote:
> > This means it generates faster code with a current gcc for your platform.
> >
> > But a future gcc might e.g. replace the whole loop with a division
> > (gcc SVN head (that will soon become gcc 4.3) already does
> > transfor
On Feb 16, 2008 9:58 AM, Willy Tarreau <[EMAIL PROTECTED]> wrote:
> Last but not least, gcc 4 tends to emit stupid checks, to the point that I
> have replaced unlikely(x) with (x) in my code when gcc >= 4 is detected. What
> I observe is that the following code :
>
> if (unlikely(p == NULL)) ..
