public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "geoffk at desire dot geoffk dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug pch/14137] [pch] ICE in cgraph_finalize_compilation_unit, at cgraphunit.c:407 Date: Sat, 27 Mar 2004 06:16:00 -0000 [thread overview] Message-ID: <20040327061647.5320.qmail@sources.redhat.com> (raw) In-Reply-To: <20040213062200.14137.mattyt-bugzilla@tpg.com.au> ------- Additional Comments From geoffk at desire dot geoffk dot org 2004-03-27 06:16 ------- Subject: Re: [pch] ICE in cgraph_finalize_compilation_unit, at cgraphunit.c:407 > While not all flags affect code generation That's not the test for whether a flag will cause problems with PCH. A good test is "If this flag could be controlled by a #pragma at the top level (that is, outside declarations), would it work?" > Seriously though, how likely is it that people will use different flags > for their PCH than for their normal compilation? What about for their abnormal compilation, or if the PCH file is not "their" PCH? One kind of case I'm thinking of is when someone has just one file that they need to compile with -fno-some-optimisation, since that optimisation turns out to make this file run slower (or crash the compiler or whatever). Or they have a flag like -fpermissive that they used to use everywhere, and are trying to eliminate, and they're about half-done. > Doesn't Joe User typicaly just use "-O[123] -g"? No, users as a group don't typically use any particular flag or combination. > I'd rather be safe and make sure all flags match than chasing flag bugs > for PCH... That would make PCH less useful. You could just remove PCH altogether, then you would have no PCH bugs to chase at all. What I think would be helpful would be to update the documentation every time a flag is discovered to be safe or unsafe for PCH. At the moment, it basically says "I don't know". I think I will create the structure for this now. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14137
next prev parent reply other threads:[~2004-03-27 6:16 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-02-13 6:22 [Bug c++/14137] New: " mattyt-bugzilla at tpg dot com dot au 2004-02-13 6:36 ` [Bug pch/14137] [pch] [unit-at-a-time] " pinskia at gcc dot gnu dot org 2004-02-13 6:42 ` [Bug pch/14137] [pch] " pinskia at gcc dot gnu dot org 2004-02-13 18:55 ` geoffk at desire dot geoffk dot org 2004-03-22 17:54 ` steven at gcc dot gnu dot org 2004-03-22 18:34 ` steven at gcc dot gnu dot org 2004-03-23 21:52 ` mmitchel at gcc dot gnu dot org 2004-03-23 22:50 ` steven at gcc dot gnu dot org 2004-03-24 22:28 ` cvs-commit at gcc dot gnu dot org 2004-03-24 22:30 ` steven at gcc dot gnu dot org 2004-03-26 23:38 ` geoffk at gcc dot gnu dot org 2004-03-26 23:53 ` stevenb at suse dot de 2004-03-27 6:16 ` geoffk at desire dot geoffk dot org [this message] 2004-03-27 10:11 ` steven at gcc dot gnu dot org 2004-03-30 17:23 ` mark at codesourcery dot com 2004-03-30 23:07 ` geoffk at desire dot geoffk dot org 2004-03-30 23:26 ` bangerth at dealii dot org 2004-04-08 19:55 ` geoffk at gcc dot gnu dot org 2004-04-08 20:16 ` mark at codesourcery dot com 2004-04-08 23:41 ` cvs-commit at gcc dot gnu dot org 2004-04-08 23:45 ` geoffk at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20040327061647.5320.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).