Re: Invalid compilation without -fno-strict-aliasing

From: H. Peter Anvin (hpa@zytor.com)
Date: Thu Feb 27 2003 - 18:55:43 EST


Followup to: <Pine.LNX.4.44.0302271234530.9696-100000@home.transmeta.com>
By author: Linus Torvalds <torvalds@transmeta.com>
In newsgroup: linux.dev.kernel
>
> On Thu, 27 Feb 2003, Daniel Jacobowitz wrote:
> >
> > We could work around both of these: disable the sign compare warning,
> > and use check_gcc to set a high number for -finline-limit...
>
> Oh, both are work-aroundable, no question about it. The same way it was
> possible to work around the broken aliasing with previous releases. I'm
> just hoping that especially the inline thing can be resolved sanely,
> otherwise we'll end up having to use something ugly like
>
> -D'inline=inline __attribute__((force_inline))'
>
> on every single command line..
>

Isn't this what compiler.h is for? If the complaint is that some
things don't include compiler.h then we may want to force it with
-include. Better all the cruft in one file IMO.

        -hpa

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: cris ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Fri Feb 28 2003 - 22:00:46 EST