public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: giovannibajo@libero.it
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, java-prs@gcc.gnu.org,
	konqueror@gmx.de, nobody@gcc.gnu.org
Subject: Re: java/6937: [2003-05-13] Segfault when deriving a class from another nested class
Date: Wed, 14 May 2003 10:36:00 -0000	[thread overview]
Message-ID: <20030514103638.27090.qmail@sources.redhat.com> (raw)

Old Synopsis: Segfault when deriving a class from another nested class
New Synopsis: [2003-05-13] Segfault when deriving a class from another nested class

State-Changed-From-To: feedback->analyzed
State-Changed-By: bajo
State-Changed-When: Wed May 14 10:36:38 2003
State-Changed-Why:
    No, this should not be closed. An ICE is never an
    accepted behaviour, it is a bug in the compiler, which
    must be fixed.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6937


                 reply	other threads:[~2003-05-14 10:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030514103638.27090.qmail@sources.redhat.com \
    --to=giovannibajo@libero.it \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    --cc=konqueror@gmx.de \
    --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).