From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8587 invoked by alias); 1 Apr 2004 01:17:07 -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 8567 invoked from network); 1 Apr 2004 01:17:04 -0000 Received: from unknown (HELO mail-out3.apple.com) (17.254.13.22) by sources.redhat.com with SMTP; 1 Apr 2004 01:17:04 -0000 Received: from mailgate2.apple.com (a17-128-100-204.apple.com [17.128.100.204]) by mail-out3.apple.com (8.12.11/8.12.11) with ESMTP id i311GxNQ001303; Wed, 31 Mar 2004 17:16:59 -0800 (PST) Received: from relay2.apple.com (relay2.apple.com) by mailgate2.apple.com (Content Technologies SMTPRS 4.3.6) with ESMTP id ; Wed, 31 Mar 2004 17:16:59 -0800 Received: from [17.201.20.159] (keatge.apple.com [17.201.20.159]) by relay2.apple.com (8.12.11/8.12.11) with ESMTP id i311GvsR024122; Thu, 1 Apr 2004 01:16:57 GMT In-Reply-To: References: <20040303083528.14400.schmid@snake.iap.physik.tu-darmstadt.de> <20040330014217.28608.qmail@sources.redhat.com> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <44BE0C58-837A-11D8-8BC9-0030657EA24A@apple.com> Content-Transfer-Encoding: 7bit Cc: gcc@gcc.gnu.org, gcc-bugzilla@gcc.gnu.org From: Geoff Keating Subject: Re: [Bug pch/14400] Cannot compile qt-x11-free-3.3.0 Date: Thu, 01 Apr 2004 01:17:00 -0000 To: Ian Lance Taylor X-SW-Source: 2004-04/txt/msg00002.txt.bz2 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. -- Geoff Keating