public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii 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: Tue, 30 Mar 2004 23:26:00 -0000	[thread overview]
Message-ID: <20040330232603.10963.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040213062200.14137.mattyt-bugzilla@tpg.com.au>


------- Additional Comments From bangerth at dealii dot org  2004-03-30 23:25 -------
In my view, if compilation time is a problem, then  
a) the project is big, 
b) we are talking about regular builds, not ones where someone 
   is playing with compiler options, and 
b) very likely people are using a makefile to build things. 
It seems very likely that within a Makefile, the number of different 
combinations of flags is relatively small (say: 2, one for debug, one 
for optimized builds), and in this case it is reasonable to ask them 
that they generate one pch file per set of flags. After all, we support 
this, by putting multiple pch files into one directory. 
 
I consider simply requiring the user to use the exact same combination 
of flags as an absolutely acceptable requirement and am not expecting 
that we get many bug reports. On the other hand, if we get reports about 
incorrect code generation due to problems with PCH, this is going to be 
significantly worse. Please also keep in mind here that PCH bugs are us 
bugmasters' worst nightmares, since they often come in huge chunks, 
involve not only a single preprocessed file but a large collection of header 
files, may involve different compilation flags for different parts of the 
build, etc. PCH bugs have been very resistant to our efforts in the past, 
and have most often been analysed by the people who know how PCH is  
implemented, rather than by bugzilla people. I therefore very strongly 
urge you to go the safe route and only allow mixing compilation flags for 
PCH generation and PCH use if we are _absolutely_ (double-checked, verifiably) 
sure that this is safe! 
 
W. 
 

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14137


  parent reply	other threads:[~2004-03-30 23:26 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
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 [this message]
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=20040330232603.10963.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: link
Be 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).