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++/7734: ICE in cp_expr_size, at cp/cp-lang.c:130
Date: Wed, 28 Aug 2002 07:06:00 -0000	[thread overview]
Message-ID: <20020828134604.22444.qmail@sources.redhat.com> (raw)

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

From: Reichelt <reichelt@igpm.rwth-aachen.de>
To: gcc-gnats@gcc.gnu.org, spigel@olvs.miee.ru, gcc-bugs@gcc.gnu.org,
        nobody@gcc.gnu.org
Cc:  
Subject: Re: c++/7734: ICE in cp_expr_size, at cp/cp-lang.c:130
Date: Wed, 28 Aug 2002 16:24:18 +0200

 Hi,
 
 the problem can be reproduced with the following code snippet:
 
 -------------------------snip here-------------------------
 struct A
 {
     A ();
     A (const A&);
     A& operator= (const A&);
 };
 
 struct { A a; } foo = { A() };
 -------------------------snip here-------------------------
 
 (with A==QString and foo==g_rgModInfo in the original example).
 
 When compiling this with the main trunk (gcc 3.3 20020816) I get the
 following error (on i686-pc-linux-gnu and mips-sgi-irix6.5):
 
 PR7734.cc: In function `void __static_initialization_and_destruction_0(int, 
    int)':
 PR7734.cc:8: internal compiler error: Internal compiler error in cp_expr_size, 
    at cp/cp-lang.c:302
 Please submit a full bug report, [etc.]
 
 This is a regression since the code compiles fine with gcc 3.0.x, 3.1
 and 3.2.
 
 Greetings,
 Volker Reichelt
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7734
 
 


             reply	other threads:[~2002-08-28 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-28  7:06 Reichelt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-09-13 14:22 nathan
2002-08-27  6:06 spigel

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=20020828134604.22444.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).