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++/38649] New: [4.4 regression] Trouble with defaulted constructors Date: Sat, 27 Dec 2008 23:52:00 -0000 [thread overview] Message-ID: <bug-38649-1771@http.gcc.gnu.org/bugzilla/> (raw) The following invalid code snippets are accepted on mainline: ======================== struct A { A(...) = default; }; ======================== ======================== struct A { A(const A&, ...) = default; }; ======================== Apparently defaultable_fn_p in cp/class.c doesn't handle the ellipsis correctly. This makes me wonder whether type_has_user_nondefault_constructor which contains similar code has the same problem. This bug can be exploited to trigger an ICE: ======================== struct A { A(...) = default; A(const A&); }; void foo() { A a; } ======================== bug.cc: In constructor 'A::A(...)': bug.cc:3: internal compiler error: Segmentation fault Please submit a full bug report, [etc.] This makes the bug a regression as the second code snippet didn't crash previous compilers. -- Summary: [4.4 regression] Trouble with defaulted constructors Product: gcc Version: 4.4.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code, accepts-invalid, 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=38649
next reply other threads:[~2008-12-27 23:52 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-12-27 23:52 reichelt at gcc dot gnu dot org [this message] 2008-12-27 23:53 ` [Bug c++/38649] " reichelt at gcc dot gnu dot org 2008-12-27 23:59 ` pinskia at gcc dot gnu dot org 2008-12-29 16:20 ` paolo dot carlini at oracle dot com 2008-12-29 21:23 ` jason at gcc dot gnu dot org 2008-12-29 23:36 ` rguenth at gcc dot gnu dot org 2009-02-11 5:23 ` jason at gcc dot gnu dot org 2009-02-11 5:25 ` jason 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-38649-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).