From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6197 invoked by alias); 5 Apr 2004 20:54:01 -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 6174 invoked from network); 5 Apr 2004 20:53:57 -0000 Received: from unknown (HELO mail-out4.apple.com) (17.254.13.23) by sources.redhat.com with SMTP; 5 Apr 2004 20:53:57 -0000 Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225]) by mail-out4.apple.com (8.12.11/8.12.11) with ESMTP id i35KvN42014325; Mon, 5 Apr 2004 13:57:23 -0700 (PDT) Received: from relay2.apple.com (relay2.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.3.6) with ESMTP id ; Mon, 5 Apr 2004 13:53:56 -0700 Received: from apple.com (mrs1.apple.com [17.201.24.248]) by relay2.apple.com (8.12.11/8.12.11) with ESMTP id i35Krcvd013870; Mon, 5 Apr 2004 20:53:39 GMT Date: Mon, 05 Apr 2004 20:54:00 -0000 Subject: Re: [Bug pch/14400] Cannot compile qt-x11-free-3.3.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v553) Cc: Geoffrey Keating , gcc@gcc.gnu.org, gcc-bugzilla@gcc.gnu.org To: Ian Lance Taylor From: Mike Stump In-Reply-To: Message-Id: <4F2BD379-8743-11D8-AD7E-003065A77310@apple.com> Content-Transfer-Encoding: 7bit X-SW-Source: 2004-04/txt/msg00232.txt.bz2 On Saturday, April 3, 2004, at 07: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? Just move the call that tries the mmap of the pch file to the validation routine. The issue there is we'd need to think about trying to mmap twice. Currently, we only ever do it once. We would try and mmap more than once when there are multiple PCH files for the same source, as we run thought all of them, trying to validate each one. > 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. This issue is known and expected and not an issue.