From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13105 invoked by alias); 29 Jan 2003 20:16:02 -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 13084 invoked by uid 71); 29 Jan 2003 20:16:01 -0000 Date: Wed, 29 Jan 2003 20:16:00 -0000 Message-ID: <20030129201601.13083.qmail@sources.redhat.com> To: aph@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Andrew Haley Subject: Re: java/8138: Compiler chokes with -O3, "fatal error reading class for second time" Reply-To: Andrew Haley X-SW-Source: 2003-01/txt/msg01705.txt.bz2 List-Id: The following reply was made to PR java/8138; it has been noted by GNATS. From: Andrew Haley To: tromey@redhat.com Cc: aph@gcc.gnu.org, adam@xwt.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, java-prs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: java/8138: Compiler chokes with -O3, "fatal error reading class for second time" Date: Wed, 29 Jan 2003 20:13:04 +0000 (GMT) Tom Tromey writes: > Andrew> Synopsis: Compiler chokes with -O3, "fatal error reading class > Andrew> for second time" > > I don't know if it is the same bug, but a current build of rhug using > 3.3 on x86 will give this error while building xalan. With -O3? > I started looking at this yesterday. Last time I tried, the test case was fine. It might be a Heisenbug. Andrew.