public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Reichelt <reichelt@igpm.rwth-aachen.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/7911: Internal compiler error in force_store_init_value, at  cp/typeck2.c:443
Date: Sun, 06 Oct 2002 06:56:00 -0000	[thread overview]
Message-ID: <20021006135600.10964.qmail@sources.redhat.com> (raw)

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

From: Reichelt <reichelt@igpm.rwth-aachen.de>
To: gcc-gnats@gcc.gnu.org, meno.abels@7d.net, gcc-bugs@gcc.gnu.org,
        nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/7911: Internal compiler error in force_store_init_value, at  cp/typeck2.c:443
Date: Sun, 6 Oct 2002 16:41:06 +0200

 Hi,
 
 
 the bug can be reproduced with the following code snippet:
 
 ----------------------------snip here--------------------------
 struct A
 {
     virtual ~A();
 };
 
 struct B
 {
     char A::* p;
     A a;
 };
 
 B b;
 ----------------------------snip here--------------------------
 
 Compiling this with gcc 3.2 ("g++ -c") causes an ICE (checked on
 mips-sgi-irix6.5 and i686-pc-linux-gnu).
 With gcc 2.95.x, 3.0.x, even 3.1 and the main trunk the code compiles
 fine. Thus, the bug is a regression on the branch and should be marked
 high priority. (I haven't got the recent head of the branch installed to
 check whether the bug has been fixed in the meantime.)
 
 Greetings,
 Volker Reichelt
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7911
 
 


             reply	other threads:[~2002-10-06 13:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-06  6:56 Reichelt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-23  5:46 reichelt
2002-09-14 12:16 Meno.Abels
2002-09-13 13:05 paolo
2002-09-13 10:06 meno.abels

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=20021006135600.10964.qmail@sources.redhat.com \
    --to=reichelt@igpm.rwth-aachen.de \
    --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).