public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/60108] [4.7/4.8/4.9 Regression] [C++11] ICE in use_thunk, at cp/method.c:340 Date: Fri, 14 Feb 2014 23:35:00 -0000 [thread overview] Message-ID: <bug-60108-4-NjKed9FuNJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60108-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60108 Volker Reichelt <reichelt at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Known to work| |4.4.0, 4.5.0, 4.6.0 Keywords| |ice-on-valid-code Last reconfirmed| |2014-02-14 CC| |reichelt at gcc dot gnu.org Ever confirmed|0 |1 Summary|ICE in use_thunk, at |[4.7/4.8/4.9 Regression] |cp/method.c:340 |[C++11] ICE in use_thunk, | |at cp/method.c:340 Target Milestone|--- |4.7.4 Known to fail| |4.7.0 --- Comment #1 from Volker Reichelt <reichelt at gcc dot gnu.org> --- Confirmed. ICEs since GCC 4.7.0. Here's a testcase without variadic templates: ============================================ template<int> struct A { virtual ~A(); }; template<typename> struct B : A<0>, A<1> { ~B() = default; }; struct C : B<bool> { C() {} }; ============================================
next prev parent reply other threads:[~2014-02-14 23:35 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-07 16:17 [Bug c++/60108] New: " doko at gcc dot gnu.org 2014-02-14 23:35 ` reichelt at gcc dot gnu.org [this message] 2014-02-21 21:58 ` [Bug c++/60108] [4.7/4.8/4.9 Regression] [C++11] " jason at gcc dot gnu.org 2014-02-21 22:15 ` jason at gcc dot gnu.org 2014-02-22 5:02 ` jason at gcc dot gnu.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-60108-4-NjKed9FuNJ@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).