From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4012 invoked by alias); 6 Apr 2004 00:39:40 -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 3977 invoked by alias); 6 Apr 2004 00:39:34 -0000 Date: Tue, 06 Apr 2004 00:39:00 -0000 Message-ID: <20040406003934.3976.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] [3.4 regression] Cannot compile qt-x11-free-3.3.0 X-Bugzilla-Reason: CC X-SW-Source: 2004-04/txt/msg00480.txt.bz2 List-Id: ------- Additional Comments From ian at wasabisystems dot com 2004-04-06 00:39 ------- Subject: Re: Cannot compile qt-x11-free-3.3.0 Geoff Keating writes: > On Apr 3, 2004, at 7:38 PM, Ian Lance Taylor wrote: > > > 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. ... > Again, my experience is that on all unix-like platforms, you *can* > always get a suitable chunk of address space in some fashion, if you > try hard enough. Even if that turns out to be true, it doesn't really help us with a gcc release when in actual fact that work has only been done on two platforms, namely Darwin and GNU/Linux. Nobody is working to fix this on mainline, much less for 3.4. You didn't like the idea of disabling PCH on other platforms, so we have to consider the case in which there is no platform specific implementation, and the default implementation of PCH, using mmap, fails. Right now, in that case, the compiler simply fails, either with a segmentation violation or a call to sorry, and it is rather difficult to work around the crash without simply discarding the PCH. Ian -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14400