From: Ian Lance Taylor <ian@wasabisystems.com>
To: Geoffrey Keating <geoffk@apple.com>
Cc: gcc@gcc.gnu.org, gcc-bugzilla@gcc.gnu.org
Subject: Re: [Bug pch/14400] Cannot compile qt-x11-free-3.3.0
Date: Sun, 04 Apr 2004 03:38:00 -0000 [thread overview]
Message-ID: <m3fzbkl8e1.fsf@gossamer.airs.com> (raw)
In-Reply-To: <3E8711F6-84DA-11D8-98AA-000A95B1F520@apple.com>
Geoffrey Keating <geoffk@apple.com> writes:
> I think that PCH that fails on one case out of a thousand is better
> than PCH that fails in one thousand cases out of one thousand.
Any thoughts on how difficult it would be to, when a PCH can not be
loaded at the correct address, skip the PCH and try for the original
header files? We'd want to issue a warning, but the result will still
be better then a compiler crash, particularly since the crash will be
awkward to work around without manually removing the PCH. Of course,
the result will not necessarily be equivalent--the original headers
might not be present, or might have been modified since the PCH was
created.
Ian
next prev parent reply other threads:[~2004-04-04 3:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040303083528.14400.schmid@snake.iap.physik.tu-darmstadt.de>
[not found] ` <20040330014217.28608.qmail@sources.redhat.com>
2004-03-30 14:02 ` Ian Lance Taylor
2004-04-01 1:17 ` Geoff Keating
[not found] ` <20040401011718.8875.qmail@sources.redhat.com>
2004-04-02 15:18 ` Ian Lance Taylor
2004-04-02 19:16 ` Geoffrey Keating
2004-04-04 3:38 ` Ian Lance Taylor [this message]
2004-04-05 20:54 ` Mike Stump
2004-04-05 22:50 ` Geoff Keating
2004-04-06 0:39 ` Ian Lance Taylor
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=m3fzbkl8e1.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=gcc-bugzilla@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@apple.com \
/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).