This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: BOOT_CFLAGS and -fomit-frame-pointer


On Fri, Mar 25, 2005 at 08:46:12AM +0100, Eric Botcazou wrote:

> Isn't that always the case in general?  With a 'make bootstrap' the compiler 
> is built by itself whereas with a bare 'make' it is built by the installed 
> compiler.  So in general the final compilers are not identical.

Umm.. you've missed my point. I'm talking about the case where the installed
compiler is an already "make bootstrapped" compiler of the same version.

Imagine this scenario:

 - GCC-4.0 is "make bootstrapped" with --prefix=/usr and installed as the
   system compiler.

 - Another GCC-4.0 is then built with a plain `make' but with
   --prefix=/opt/gcc-test1 and installed

 - Another GCC-4.0 is then built with `make bootstrap' but with
   --prefix=/opt/gcc-test2 and installed

The compilers in /opt/gcc-test1 and /opt/gcc-test2 are different because 1
was built with -fomit-frame-pointer and the other one wasn't.

To reiterate, this is different behaviour from past GCC releases, and it
appears wrong to me.

> What prevents you from setting CFLAGS="-O2 -fomit-frame-pointer" if you
> happen to be rebuilding the compiler with an installed version of itself?

Nothing at all. I already mentioned the issue is easily worked around. But
that is not the point. My point is that the behaviour seems wrong, but I
wasn't sure whether it was worth entering in BZ, hence my raising the issue
here for insight by GCC developers. Not to worry.. it's no big deal.

Regards
Greg


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]