This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/30810] top-level BOOT_CFLAGS not being used for bootstrapping
- From: "sdack at gmx dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 18 Feb 2007 22:12:03 -0000
- Subject: [Bug bootstrap/30810] top-level BOOT_CFLAGS not being used for bootstrapping
- References: <bug-30810-14108@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #7 from sdack at gmx dot de 2007-02-18 22:12 -------
I dug a bit deeper and should now get my gcc compiled with a load full of
options. It is compiling right now. The idea is to get a highly optimized
output as well as to cause high stress to gcc. However, there is a file called
gcc-4.1.2/config/mh-x86omitf, which hard-codes BOOT_CFLAGS. This value can not
be over-written by an environment variable, through an argument to make or by
specifying --with-boot-cflags=... to configure. The file gets included and then
seems to be untouchable. I therefore edited it. Why libcpp and other parts are
being compiled with no CFLAGS when they surely could use some optimization I do
not yet now. The whole concept of autoconf/automake blurrs it to an extend
where I loose my interest.
... The compile now aborted with an internal compiler error. So much for that
*smirk*.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30810