public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	snyder@fnal.gov
Subject: Re: c++/8850: [3.3 regression] SEGV in push_local_name on invalid code
Date: Fri, 06 Dec 2002 15:35:00 -0000	[thread overview]
Message-ID: <20021206233551.19898.qmail@sources.redhat.com> (raw)

Old Synopsis: g++ 3.3: SEGV in push_local_name on invalid code
New Synopsis: [3.3 regression] SEGV in push_local_name on invalid code

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Fri Dec  6 15:35:50 2002
State-Changed-Why:
    The code is really completely illegal. But 3.3 should not
    decide to ICE on it, in particularly please not if previous
    versions of gcc did not.
    
    BTW, please file your reports in category "C++". The
    "pending -- vategory for faulty PRs" category does not
    mean that the code that triggers the problem is bogus,
    but that the report itself is bogus.

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


                 reply	other threads:[~2002-12-06 23:35 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=20021206233551.19898.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=snyder@fnal.gov \
    /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).