This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/16504] [3.5 Regression] ICE in gmon-sol2, stage2
- From: "James dot W dot Mckelvey at jpl dot nasa dot gov" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Jul 2004 15:19:33 -0000
- Subject: [Bug bootstrap/16504] [3.5 Regression] ICE in gmon-sol2, stage2
- References: <20040712224154.16504.James.W.Mckelvey@jpl.nasa.gov>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From James dot W dot Mckelvey at jpl dot nasa dot gov 2004-07-14 15:19 -------
(In reply to comment #3)
> Confirmed with gcc version 3.5.0 20040714 (experimental) and BOOT_CFLAGS=-O.
> The regular bootstrap (i.e. without setting BOOT_CFLAGS) is not affected.
>
> Note that you should not set CFLAGS when bootstrapping the compiler, because it
> may trigger bugs in the bootstrap compiler, which we don't want to mix with bugs
> in the bootstrapped compiler.
>
I understand. But somebody better fix the instructions on the web site, which
show not only that but -fno-implicit-templates, the subject of another recent
bug report.
http://gcc.gnu.org/install/build.html
If you want to save additional space during the bootstrap and in the final
installation as well, you can build the compiler binaries without debugging
information as in the following example. This will save roughly 40% of disk
space both for the bootstrap and the final installation. (Libraries will still
contain debugging information.)
make CFLAGS='-O' LIBCFLAGS='-g -O2' \
LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap
It does talk about "non-standard CFLAGS" a few paragraphs below this, but only
in referring to libiberty. It's unclear what is meant by "non-standard".
What is needed is an actual example of a recommended command line.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16504