public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/8511: (hopefully) reproducible cc1plus SIGSEGV.
Date: Wed, 20 Nov 2002 18:16:00 -0000	[thread overview]
Message-ID: <20021114193601.23176.qmail@sources.redhat.com> (raw)

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


             reply	other threads:[~2002-11-14 19:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-20 18:16 Zack Weinberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-22 10:46 Wolfgang Wieser
2002-11-20 18:12 Wolfgang Wieser
2002-11-19 18:25 Zack Weinberg
2002-11-19 18:16 Wolfgang Wieser
2002-11-10 13:16 Volker Reichelt
2002-11-10 12:46 Zack Weinberg
2002-11-10  5:26 wwieser
2002-11-09 15:54 reichelt
2002-11-09  4:36 wwieser

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=20021114193601.23176.qmail@sources.redhat.com \
    --to=zack@codesourcery.com \
    --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).