This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug pch/14137] [pch] ICE in cgraph_finalize_compilation_unit, at cgraphunit.c:407
- From: "stevenb at suse dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 26 Mar 2004 23:53:47 -0000
- Subject: [Bug pch/14137] [pch] ICE in cgraph_finalize_compilation_unit, at cgraphunit.c:407
- References: <20040213062200.14137.mattyt-bugzilla@tpg.com.au>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From stevenb at suse dot de 2004-03-26 23:53 -------
Subject: Re: [pch] ICE in cgraph_finalize_compilation_unit, at cgraphunit.c:407
On Saturday 27 March 2004 00:38, geoffk at gcc dot gnu dot org wrote:
> ------- Additional Comments From geoffk at gcc dot gnu dot org 2004-03-26 23:38 -------
> Most flags shouldn't affect acceptance/rejection of a PCH.
While not all flags affect code generation, it doesn't seem unreasonable
to make sure that at least all -m*, -f*, and -g* flags are the same. It
doesn't sound very safe, or maintainable, to keep track of which flags
do affect PCH and which don't. Getting all the GTYs right has turned
out to be hard enough ;-)
Seriously though, how likely is it that people will use different flags
for their PCH than for their normal compilation? Doesn't Joe User
typicaly just use "-O[123] -g"?
I'd rather be safe and make sure all flags match than chasing flag bugs
for PCH...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14137