public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/26071] New: [4.0/4.1/4.2 regression] ICE declaring destructor virtual and static Date: Thu, 02 Feb 2006 09:01:00 -0000 [thread overview] Message-ID: <bug-26071-1771@http.gcc.gnu.org/bugzilla/> (raw) The following invalid code snippet causes an ICE: =============================== struct A { virtual static ~A(); }; =============================== ' Segmentation fault Please submit a full bug report, [etc.] This a regression from GCC 3.4.x. Before we got the error message: bug.cc:3: error: member `A' cannot be declared both virtual and static which is not quite correct, but tolerable. Will post patch soon. -- Summary: [4.0/4.1/4.2 regression] ICE declaring destructor virtual and static Product: gcc Version: 4.2.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code, monitored Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: reichelt at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26071
next reply other threads:[~2006-02-02 9:01 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-02 9:01 reichelt at gcc dot gnu dot org [this message] 2006-02-02 9:07 ` [Bug c++/26071] " reichelt at gcc dot gnu dot org 2006-02-02 9:07 ` reichelt at gcc dot gnu dot org 2006-02-08 11:21 ` reichelt at gcc dot gnu dot org 2006-02-08 11:23 ` reichelt at gcc dot gnu dot org 2006-02-08 11:26 ` reichelt at gcc dot gnu dot org 2006-02-08 11:27 ` reichelt at gcc dot gnu dot org
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=bug-26071-1771@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).