public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: reichelt@igpm.rwth-aachen.de
To: deller@gmx.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c++/8625: [3.3 regression] ICE in cp_convert_parm_for_inlining, at cp/call.c:4304
Date: Sun, 24 Nov 2002 10:47:00 -0000	[thread overview]
Message-ID: <20021118214948.32644.qmail@sources.redhat.com> (raw)

Old Synopsis: ice on valid c++ code
New Synopsis: [3.3 regression] ICE in cp_convert_parm_for_inlining, at cp/call.c:4304

State-Changed-From-To: open->analyzed
State-Changed-By: reichelt
State-Changed-When: Mon Nov 18 13:49:46 2002
State-Changed-Why:
    Confirmed.
    
    The ICE can be reproduced with the following code snippet:
    
    ---------------------snip here--------------------------
    struct A
    {
        ~A();
    };
    
    struct B
    {
        B( A ) {}
    };
    
    const A foo();
    
    B b(foo());
    ---------------------snip here--------------------------
    
    The error message is (just compile with "g++ -O -c"):
    
    In file included from PR8625.cc:13:
    PR8625.cc: In function `void __static_initialization_and_destruction_0(int, 
       int)':
    PR8625.cc:8: internal compiler error: in cp_convert_parm_for_inlining, at 
       cp/call.c:4304
    Please submit a full bug report,
    
    Only mainline is affected (gcc 3.3 20021111). Thus, we have a regression.
    I can reproduce the bug on i686-pc-liunx-gnu and mips-sgi-irix6.5.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8625


             reply	other threads:[~2002-11-18 21:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-24 10:47 reichelt [this message]
2002-12-09 23:24 mmitchel

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=20021118214948.32644.qmail@sources.redhat.com \
    --to=reichelt@igpm.rwth-aachen.de \
    --cc=deller@gmx.de \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --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).