public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: aph@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/8063: Compiler chokes with -O3, "fatal error reading class for second time"
Date: Fri, 27 Sep 2002 11:36:00 -0000	[thread overview]
Message-ID: <20020927183602.25398.qmail@sources.redhat.com> (raw)

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

From: Andrew Haley <aph@redhat.com>
To: Adam Megacz <adam@megacz.com>
Cc: tromey@redhat.com, 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/8063: Compiler chokes with -O3, "fatal error reading class for second time"
Date: Fri, 27 Sep 2002 19:30:14 +0100 (BST)

 Adam Megacz writes:
  > 
  > Andrew Haley <aph@redhat.com> writes:
  > > Are you totally sure that this was a clean build from clean source?
  > 
  > Yes.
  > 
  > Also, keep in mind that we've found discrepancies in compiler behavior
  > before based on what compiler was used to compile the compiler.
  > Specifically, in a previous thread, people who used 2.95 to build 3.x
  > got crashes, while people who used 3.1 to build 3.x (such as you,
  > Andrew) did not get crashes:
  > 
  >   http://gcc.gnu.org/ml/java/2002-09/msg00114.html
 
 Well, we don't know that was the cause of the problem.  It might
 equally have been system libraries, for example.
 
 Andrew.
 


             reply	other threads:[~2002-09-27 18:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-27 11:36 Andrew Haley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-04  2:22 aph
2002-09-27 11:26 Adam Megacz
2002-09-27 10:56 Andrew Haley
2002-09-27 10:46 Adam Megacz
2002-09-27  8:46 Tom Tromey
2002-09-27  8:25 aph
2002-09-26 19:46 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=20020927183602.25398.qmail@sources.redhat.com \
    --to=aph@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).