From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-prs-return-18428-listarch-gcc-prs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 13675 invoked by alias); 8 May 2002 03:56:01 -0000
Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-prs/>
List-Post: <mailto:gcc-prs@gcc.gnu.org>
List-Help: <mailto:gcc-prs-help@gcc.gnu.org>
Sender: gcc-prs-owner@gcc.gnu.org
Received: (qmail 13644 invoked by uid 71); 8 May 2002 03:56:00 -0000
Date: Tue, 07 May 2002 20:56:00 -0000
Message-ID: <20020508035600.13643.qmail@sources.redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
From: "Billinghurst, David \(CRTS\)" <David.Billinghurst@riotinto.com>
Subject: RE: bootstrap/6539: 3.2 bootstrap failure on irix6.5 - fixproto
Reply-To: "Billinghurst, David \(CRTS\)" <David.Billinghurst@riotinto.com>
X-SW-Source: 2002-05/txt/msg00212.txt.bz2
List-Id: <gcc-prs.sourceware.org>

The following reply was made to PR bootstrap/6539; it has been noted by GNATS.

From: "Billinghurst, David (CRTS)" <David.Billinghurst@riotinto.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>,
	<gcc-bugs@gcc.gnu.org>,
	<gcc-gnats@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>,
	<jakub@redhat.com>,
	<nobody@gcc.gnu.org>
Cc:  
Subject: RE: bootstrap/6539: 3.2 bootstrap failure on irix6.5 - fixproto
Date: Wed, 8 May 2002 13:30:29 +1000

 Kaveh and Jakub,
 
 You are right and I am wrong.  I messed up my binary search.
 The error WAS present at 19:45, before Jakub's patch went in.
 
 I should have it nailed shortly.
 
 -----Original Message-----
 From: Kaveh R. Ghazi [mailto:ghazi@caip.rutgers.edu]
 Sent: Tuesday, 7 May 2002 11:02=20
 To: Billinghurst, David (CRTS); gcc-bugs@gcc.gnu.org;
 gcc-gnats@gcc.gnu.org; gcc-prs@gcc.gnu.org; jakub@redhat.com;
 nobody@gcc.gnu.org
 Subject: RE: bootstrap/6539: 3.2 bootstrap failure on irix6.5 - fixproto
 
 
  > From: Kaveh R. Ghazi [mailto:ghazi@caip.rutgers.edu]
  >=20
  > Any progress on this PR?  I see the same failure on irix6.2 also.
  > I've added myself to the cc list in the PR, please keep me in the =
 loop
  > on any progress.  Thanks.
 
 David, your report indicates you suspect that Jakub's reload1.c patch
 caused the problem.  However I note that fix-header is run in stage1
 and not compiled by or linked with the relevant reload1.o. :-)
 
 Based on that and the details of your backtrace, I suspect instead
 some kind of libcpp bug.  If you agree, would you please gather the
 input headers for the particular crash and send them to Zack and/or
 Neil so they can help debug?
 
 		Thanks,
 		--Kaveh
 --
 Kaveh R. Ghazi			Director of Systems Architecture
 ghazi@caip.rutgers.edu		Qwest Global Services