public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rassahah@neofonie.de To: gcc-gnats@gcc.gnu.org Subject: c++/8461: internal compiler error stabilize_throw_expr Date: Tue, 05 Nov 2002 04:06:00 -0000 [thread overview] Message-ID: <20021105115832.30997.qmail@sources.redhat.com> (raw) >Number: 8461 >Category: c++ >Synopsis: internal compiler error stabilize_throw_expr >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-legal-code >Submitter-Id: net >Arrival-Date: Tue Nov 05 04:06:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: rassahah@neofonie.de >Release: gcc-3.3 cvs of 5-Nov-2002 >Organization: >Environment: i686-pc-linux-gnu gcc-3.3 compiled with gcc-3.2 and itself >Description: compiler error on given code (in How-To-Repeat); Exception is thrown. The constructor of the exception has an object argument wich itself has a virtual destructor. This seems to be necessary for reproducing the bug. The bug is new in in the 3.3 version of the compiler 2.95 up to 3.2 dont show it. farewell-message of compiler: test1.cc: In function `void foo()': test1.cc:12: internal compiler error: in stabilize_throw_expr, at cp/except.c: 611 Please submit a full ... >How-To-Repeat: use the following program for g++, options dont seem to change effect, #includes are not needed: struct String { virtual ~String (); }; struct Exception { Exception (const String s) {} }; const String getstring () { return String (); } void foo () { throw Exception (getstring ()); // doesnt compile } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-11-05 12:06 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021105115832.30997.qmail@sources.redhat.com \ --to=rassahah@neofonie.de \ --cc=gcc-gnats@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: linkBe 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).