public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Giovanni Bajo" <giovannibajo@libero.it>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10438: [3.3 regression] [hppa] Segfault when building jade
Date: Sat, 19 Apr 2003 15:06:00 -0000	[thread overview]
Message-ID: <20030419150601.19862.qmail@sources.redhat.com> (raw)

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

From: "Giovanni Bajo" <giovannibajo@libero.it>
To: <gcc-gnats@gcc.gnu.org>,
	<parisc-linux@lists.parisc-linux.org>,
	<tausq@debian.org>,
	<gcc-bugs@gcc.gnu.org>,
	<debian-gcc@lists.debian.org>,
	<nobody@gcc.gnu.org>,
	<gcc-prs@gcc.gnu.org>
Cc: "Wolfgang Bangerth" <bangerth@ices.utexas.edu>
Subject: Re: c++/10438: [3.3 regression] [hppa] Segfault when building jade
Date: Sat, 19 Apr 2003 17:05:11 +0200

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p
 r=10438
 
 Confirmed. Slightly reduced testcase:
 
 --------------------------------
 struct Foo
 {
     struct Nested1
     {
         enum E
         {
             v1,v2,v3,v4,v5,v6
         } E;
     };
 
     struct Nested2 : public Nested1
     {};
 };
 
 --------------------------------
 pr10438.cpp:12: internal compiler error: Segmentation fault
 Please submit a full bug report,
 
 
 It looks like a memory corruption bug, while playing with it I had the ICE
 on and off simply by changing variable names. You can also see that the ICE
 disappears if you remove some elements from within the enum. It seems that
 the culript is the variable defined with the same name of the enum type.
 
 It's a regression on 3.3 and 3.4 with respect to 3.2, where it compiles
 fine.
 
 Giovanni Bajo
 


             reply	other threads:[~2003-04-19 15:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-19 15:06 Giovanni Bajo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-20 17:49 nathan
2003-04-19 15:36 Randolph Chung
2003-04-19  5:16 Randolph Chung

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=20030419150601.19862.qmail@sources.redhat.com \
    --to=giovannibajo@libero.it \
    --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).