From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19937 invoked by alias); 6 Dec 2002 23:35:53 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 19899 invoked by uid 61); 6 Dec 2002 23:35:51 -0000 Date: Fri, 06 Dec 2002 15:35:00 -0000 Message-ID: <20021206233551.19898.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, snyder@fnal.gov From: bangerth@dealii.org Reply-To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, snyder@fnal.gov, gcc-gnats@gcc.gnu.org Subject: Re: c++/8850: [3.3 regression] SEGV in push_local_name on invalid code X-SW-Source: 2002-12/txt/msg00420.txt.bz2 List-Id: 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