From: Ian Lance Taylor <ian@wasabisystems.com>
To: geoffk@apple.com
Cc: gcc-bugzilla@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: [Bug pch/14400] Cannot compile qt-x11-free-3.3.0
Date: Tue, 30 Mar 2004 14:02:00 -0000 [thread overview]
Message-ID: <m31xnabyph.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20040330014217.28608.qmail@sources.redhat.com>
"geoffk at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:
> I believe I saw this on Darwin before implementing the scheme it uses now. I don't believe there's any
> solution to the general problem that doesn't know more about the host's memory map; the current
> generic solution is just a heuristic and is not reliable. For reliable operation, *especially* on x86-linux-
> gnu, I recommend implementing a solution like Darwin's. That would also fix 14206.
PR 14206 is fixed on mainline by RTH's patch. For 3.4 I put in a doc
fix.
> This is not a problem that you can solve with a 'quick fix'.
Perhaps for 3.4 we should disable PCH for any target other than
Darwin. It seems to me that it is a bad idea to include an unreliable
feature. It's particularly unfortunate that it causes gcc 3.4 to fail
to build a popular package (qt-x11-free) on a popular platform
(GNU/Linux). It's even more unfortunate that the failure currently
shows up as a random compiler crash.
I will investigate further on mainline.
Ian
next parent reply other threads:[~2004-03-30 7:06 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 [this message]
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
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=m31xnabyph.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).