public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/7838: Internal compiler error in make_class_data, at java/class.c
Date: Thu, 05 Sep 2002 19:26:00 -0000	[thread overview]
Message-ID: <20020906022601.16955.qmail@sources.redhat.com> (raw)

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

From: Tom Tromey <tromey@redhat.com>
To: cassio@pucsp.br
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: java/7838: Internal compiler error in make_class_data, at java/class.c
Date: 05 Sep 2002 20:23:29 -0600

 >>>>> ">" == cassio  <cassio@pucsp.br> writes:
 
 >> Number:         7838
 >> Synopsis:       Internal compiler error in make_class_data, at java/class.c
 
 >> Client.java:1: Internal compiler error in make_class_data, at java/class.c:1676
 
 >> It's necessary to have the java class sources in the path.
 >> I'm working with the j2sdk1.3.1/src/share/classes/ directory.
 
 This is definitely a bug -- you should never be able to get an
 internal compiler error.
 
 However, using gcj with a class library other than libgcj doesn't
 work.  (It could be made to work when generating bytecode, but not
 when generating native code.)  So the likely resolution of this
 problem will be to turn the ICE into a "don't do that" error.  FYI.
 
 Tom


             reply	other threads:[~2002-09-06  2:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-05 19:26 Tom Tromey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-08  6:47 aph
2002-09-05 10:36 cassio

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=20020906022601.16955.qmail@sources.redhat.com \
    --to=tromey@redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).