From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4318 invoked by alias); 14 Dec 2001 16:56:01 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 4295 invoked by uid 71); 14 Dec 2001 16:56:01 -0000 Date: Fri, 14 Dec 2001 08:56:00 -0000 Message-ID: <20011214165601.4293.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Reichelt Subject: Re: bootstrap/5043 Reply-To: Reichelt X-SW-Source: 2001-12/txt/msg00828.txt.bz2 List-Id: The following reply was made to PR bootstrap/5043; it has been noted by GNATS. From: Reichelt To: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: bootstrap/5043 Date: Fri, 14 Dec 2001 18:02:24 +0100 A little update: The bootstrap-failure only seems to occur, if I use gcc 3.0.x to start the bootstrap process. With gcc 2.95.3 and SGI's native compiler I can do a full bootstrap (there are some problems with the configure script - see PR 5117 - but nothing severe). Maybe it's not a bootstrap-failure of 3.1, but a code generation bug in 3.0.x, that is exposed by the bootstrap process. Greetings, Volker http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=5043&database=gcc