From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22941 invoked by alias); 30 Mar 2004 07:07:12 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 22888 invoked by alias); 30 Mar 2004 07:07:10 -0000 Date: Tue, 30 Mar 2004 07:07:00 -0000 Message-ID: <20040330070710.22887.qmail@sources.redhat.com> From: "ian at wasabisystems dot com" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20040303083528.14400.schmid@snake.iap.physik.tu-darmstadt.de> References: <20040303083528.14400.schmid@snake.iap.physik.tu-darmstadt.de> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug pch/14400] Cannot compile qt-x11-free-3.3.0 X-Bugzilla-Reason: CC X-SW-Source: 2004-03/txt/msg03387.txt.bz2 List-Id: ------- Additional Comments From ian at wasabisystems dot com 2004-03-30 07:07 ------- Subject: Re: Cannot compile qt-x11-free-3.3.0 "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 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14400