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++/38701] New: [4.4 regression] ICE with defaulted function Date: Fri, 02 Jan 2009 14:53:00 -0000 [thread overview] Message-ID: <bug-38701-1771@http.gcc.gnu.org/bugzilla/> (raw) The following invalid code snippet triggers an ICE on the trunk: ====================================== void foo() = default; ====================================== bug.cc:1: error: 'void foo()' cannot be defaulted bug.cc:1: internal compiler error: Segmentation fault Please submit a full bug report, [etc.] A similar code snippet triggers an ICE in a different place: ====================================== namespace { void foo() = default; } ====================================== bug.cc:3: error: 'void<unnamed>::foo()' cannot be defaulted bug.cc:3: internal compiler error: tree check: expected class 'type', have 'declaration' (namespace_decl) in synthesize_method, at cp/method.c:758 Please submit a full bug report, [etc.] This is a recent regression on the trunk, introduced between 2008-11-20 and 2008-12-06. -- Summary: [4.4 regression] ICE with defaulted function Product: gcc Version: 4.4.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code, error-recovery, 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=38701
next reply other threads:[~2009-01-02 14:53 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-02 14:53 reichelt at gcc dot gnu dot org [this message] 2009-01-02 14:54 ` [Bug c++/38701] " reichelt at gcc dot gnu dot org 2009-01-02 15:36 ` paolo dot carlini at oracle dot com 2009-01-02 20:17 ` pinskia at gcc dot gnu dot org 2009-01-03 3:53 ` jason at gcc dot gnu dot org 2009-01-05 11:31 ` rguenth at gcc dot gnu dot org 2009-01-05 17:52 ` jason at gcc dot gnu dot org 2009-01-05 17:53 ` jason at gcc dot gnu dot org 2009-01-05 18:33 ` jakub 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-38701-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).