This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: -fobey-inline (was Re: gcc and inlining)
- From: Andi Kleen <ak at suse dot de>
- To: Andrew Haley <aph at redhat dot com>
- Cc: neil at daikokuya dot co dot uk, lars dot segerlund at comsys dot se, gcc at gcc dot gnu dot org
- Date: 13 Mar 2003 22:49:38 +0100
- Subject: Re: -fobey-inline (was Re: gcc and inlining)
- References: <200303131400.h2DE0ZB24570@pc960.cambridge.arm.com.suse.lists.egcs> <3E709381.5090500@comsys.se.suse.lists.egcs> <20030313192518.GF21522@daikokuya.co.uk.suse.lists.egcs> <15984.56422.24671.261942@cuddles.cambridge.redhat.com.suse.lists.egcs>
Andrew Haley <aph at redhat dot com> writes:
> Yeah. I gotta admit that
>
> #define inline __inline__ __attribute__((always_inline))
>
> solves the problem so completely that an new gcc option is unnecessary.
> It can even be written "gcc -D inline=__inline__ __attribute__((always_inline))"
Actually not. First you forgot the `"'s, but even when you add them
they are in grave danger of being eaten by various Makefiles who
first execute a shell script or similar to run the compiler.
I had this problem with the Linux kernel Makefiles. The only thing that worked
reliable was
-include file
in the Makefile and putting the define into file. But that's quite ugly.
-fobey-inline would be much easier.
-Andi