public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Michael Koch <konqueror@gmx.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/6937: Segfault when deriving a class from another nested class
Date: Tue, 13 May 2003 18:07:00 -0000	[thread overview]
Message-ID: <20030513180603.5288.qmail@sources.redhat.com> (raw)

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

From: Michael Koch <konqueror@gmx.de>
To: Dara Hazeghi <dhazeghi@stanford.edu>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: java/6937: Segfault when deriving a class from another nested class
Date: Tue, 13 May 2003 20:03:23 +0200

 =2D----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA1
 
 Am Dienstag, 13. Mai 2003 19:13 schrieb Dara Hazeghi:
 > On Tuesday, May 13, 2003, at 03:35 AM, Michael Koch wrote:
 > > -----BEGIN PGP SIGNED MESSAGE-----
 > > Hash: SHA1
 > >
 > > Am Montag, 12. Mai 2003 22:04 schrieben Sie:
 > >> Begin forwarded message:
 > >>> From: Dara Hazeghi <dhazeghi@yahoo.com>
 > >>> Date: Mon May 12, 2003  12:39:59 PM US/Pacific
 > >>> To: konqueror@gmx.de, gcc-gnats@gcc.gnu.org
 > >>> Subject: Re: java/6937: Segfault when deriving a class from
 > >>> another nested class
 > >>>
 > >>> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=3Dview%20audit-
 > >>> trail&database=3Dgcc&pr=3D6937
 > >>>
 > >>> Hello,
 > >>>
 > >>> could the submitter please confirm if this problem still occurs
 > >>> with gcc 3.3 prerelease or mainline cvs? On both I get errors
 > >>> compiling:
 > >>>
 > >>> ./Container.java:1: Class `Container' already defined in
 > >>> Container.java:1.
 > >>>    public class Container
 > >>>                 ^
 > >>> ./Container.java:5: confused by earlier errors, bailing out
 > >>> bash-2.04$ /tmp/dara1/bin/gcj -C Container.java Derived.java
 > >>> ./Container.java:1: error: Class `Container' already defined in
 > >>> Container.java:1.
 > >>>    public class Container
 > >>>                 ^
 > >>> ./Container.java:5: confused by earlier errors, bailing out
 > >>>
 > >>> Thanks,
 > >>>
 > >>> Dara
 > >
 > > Yes I still get the segfault with trunk-cvs from 20030513.
 > >
 > > But I do get an error with JDK 1.4.1 now too. My testcase is
 > > obviously wrong. I think this can be closed.
 >
 > Do you just want to close it, or mark it as an ICE on illegal code?
 > Thanks,
 
 Just close it. I think I remember that Tom said that an ICE on illegal=20
 code is okay.
 
 Michael
 =2D --=20
 Homepage: http://www.worldforge.org/
 =2D----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.1 (GNU/Linux)
 
 iD8DBQE+wTNsWSOgCCdjSDsRAoFiAJ4iT0Hjtrfw6ZM/lc37m39dFjq2OgCeOgme
 ujFxheUeRUa7RiUHO/s7DdU=3D
 =3DazXx
 =2D----END PGP SIGNATURE-----
 


             reply	other threads:[~2003-05-13 18:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-13 18:07 Michael Koch [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-13 17:16 Dara Hazeghi
2003-05-13  6:38 steven
2003-05-12 19:46 Dara Hazeghi
2002-06-05 11:16 konqueror

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=20030513180603.5288.qmail@sources.redhat.com \
    --to=konqueror@gmx.de \
    --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).