From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8910 invoked by alias); 1 Apr 2004 01:17:19 -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 8871 invoked by alias); 1 Apr 2004 01:17:17 -0000 Date: Thu, 01 Apr 2004 01:17:00 -0000 Message-ID: <20040401011717.8870.qmail@sources.redhat.com> From: "geoffk at apple 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-04/txt/msg00002.txt.bz2 List-Id: ------- Additional Comments From geoffk at apple dot com 2004-04-01 01:17 ------- Subject: Re: Cannot compile qt-x11-free-3.3.0 On Mar 29, 2004, at 11:06 PM, Ian Lance Taylor wrote: > "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. I've now caught up enough that I read RTH's patch (I've been on vacation). Yes, that patch should fix this problem too. I'd suggest backporting it to 3.4. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14400