From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22582 invoked by alias); 30 Mar 2004 07:06:59 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 22527 invoked from network); 30 Mar 2004 07:06:57 -0000 Received: from unknown (HELO yosemite.airs.com) (209.128.65.135) by sources.redhat.com with SMTP; 30 Mar 2004 07:06:57 -0000 Received: (qmail 12116 invoked by uid 10); 30 Mar 2004 07:06:57 -0000 Received: (qmail 4331 invoked by uid 500); 30 Mar 2004 07:06:50 -0000 From: Ian Lance Taylor 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 References: <20040303083528.14400.schmid@snake.iap.physik.tu-darmstadt.de> <20040330014217.28608.qmail@sources.redhat.com> Date: Tue, 30 Mar 2004 14:02:00 -0000 In-Reply-To: <20040330014217.28608.qmail@sources.redhat.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2004-03/txt/msg01705.txt.bz2 "geoffk at gcc dot gnu dot 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