public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: aph@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/8138: Compiler chokes with -O3, "fatal error reading class for second time"
Date: Wed, 29 Jan 2003 20:16:00 -0000 [thread overview]
Message-ID: <20030129201601.13066.qmail@sources.redhat.com> (raw)
The following reply was made to PR java/8138; it has been noted by GNATS.
From: Tom Tromey <tromey@redhat.com>
To: aph@gcc.gnu.org
Cc: adam@xwt.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
java-prs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, aph@gcc.gnu.org
Subject: Re: java/8138: Compiler chokes with -O3, "fatal error reading class for second time"
Date: 29 Jan 2003 13:00:59 -0700
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. I started
looking at this yesterday.
Tom
next reply other threads:[~2003-01-29 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 20:16 Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-15 8:36 Adam Megacz
2003-01-29 21:36 Tom Tromey
2003-01-29 20:16 Andrew Haley
2003-01-29 20:04 aph
2002-10-04 2:19 aph
2002-10-03 23:26 adam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030129201601.13066.qmail@sources.redhat.com \
--to=tromey@redhat.com \
--cc=aph@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).