c++/8511: (hopefully) reproducible cc1plus SIGSEGV.

[Zack Weinberg]

The following reply was made to PR c++/8511; it has been noted by GNATS.

From: Zack Weinberg <zack@codesourcery.com>
To: Wolfgang Wieser <wwieser@gmx.de>
Cc: mark@codesourcery.com,  Volker Reichelt <reichelt@igpm.rwth-aachen.de>,
	  gcc-gnats@gcc.gnu.org,  gcc-bugs@gcc.gnu.org
Subject: Re: c++/8511: (hopefully) reproducible cc1plus SIGSEGV.
Date: Thu, 14 Nov 2002 11:29:23 -0800

 Wolfgang Wieser <wwieser@gmx.de> writes:
 
 >> That prevents the invalid access.  Your test case then carries on to
 >> crash in c_expand_expr, which is the other bug that we already know
 >> about, and Volker found a reduced test case for.  I'm cc:ing Mark for
 >> comments, he's a lot more familiar with this part of the compiler than
 >> I am.  I'm a bit concerned that this does not happen when unrelated
 >> parts of the code are changed; the original data corruption could be
 >> even earlier.
 
 FYI, I will be posting an updated patch for the data corruption bug
 later today; comments would be nice.
 
 > Okay, I just found the e-mail containing a test case triggering a bug in 
 > c_expand_expr: 
 >
 > ----------------------------snip here---------------------------
 > template<int N> class A
 > {
 >     template<int I,int J> friend int foo();
 > };
 >
 > A<0> a;
 >
 > template<int I,int J> int foo() { return J; }
 >
 > void bar() { foo<0,0>(); }
 > ----------------------------snip here---------------------------
 >
 > This test case was generously provided by Volker Reichelt .. :) 
 > and can be accessed as problem report 6971 (filed by me). 
 
 This bug is still reproducible with the 3.2.1 prerelease and with CVS
 HEAD.  I get a different ICE with 2.95.
 
 Hopefully this will get fixed in 3.3, but I cannot promise anything.
 Since this bug is c++/6971, do you agree we can close c++/8511 once
 the segmentation fault is patched?
 
 zw