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++/28301] New: [4.0/4.1/4.2 regression] ICE with broken specialization Date: Fri, 07 Jul 2006 14:25:00 -0000 [thread overview] Message-ID: <bug-28301-1771@http.gcc.gnu.org/bugzilla/> (raw) The following invalid code snippet triggers an ICE since GCC 3.4.0: =========================================== template<typename> struct A { template<int> void foo() // missing ; }; template<> struct A<void> { template<int> void foo(); }; void bar() { A<void> a; a.foo<0>(); } =========================================== bug.cc:4: error: expected initializer before '}' token bug.cc:6: error: explicit specialization in non-namespace scope 'struct A< <template-parameter-1-1> >' bug.cc:6: error: enclosing class templates are not explicitly specialized bug.cc:6: error: template parameters not used in partial specialization: bug.cc:6: error: '<template-parameter-1-1>' bug.cc:15: error: expected `}' at end of input bug.cc: In member function 'void A< <template-parameter-1-1> >::bar()': bug.cc:14: internal compiler error: in retrieve_specialization, at cp/pt.c:819 Please submit a full bug report, [etc.] -- Summary: [4.0/4.1/4.2 regression] ICE with broken specialization Product: gcc Version: 4.2.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=28301
next reply other threads:[~2006-07-07 14:25 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-07-07 14:25 reichelt at gcc dot gnu dot org [this message] 2006-07-07 14:26 ` [Bug c++/28301] " reichelt at gcc dot gnu dot org 2006-07-17 3:10 ` mmitchel at gcc dot gnu dot org 2006-09-03 6:30 ` pinskia at gcc dot gnu dot org 2006-09-09 13:20 ` lmillward at gcc dot gnu dot org 2006-09-09 13:20 ` patchapp at dberlin dot org 2006-10-05 19:58 ` [Bug c++/28301] [4.0/4.1 " reichelt at gcc dot gnu dot org 2007-02-03 17:57 ` gdr at gcc dot gnu dot org 2007-02-03 20:50 ` pinskia at gcc dot gnu dot org 2007-02-14 9:25 ` mmitchel at gcc dot gnu dot org 2008-07-04 15:41 ` [Bug c++/28301] [4.1 " jsm28 at gcc dot gnu dot org 2009-03-28 21:41 ` [Bug c++/28301] [4.3/4.4/4.5 " reichelt at gcc dot gnu dot org 2009-03-28 21:56 ` hjl dot tools at gmail dot com 2009-03-31 17:37 ` hjl dot tools at gmail dot com 2009-04-10 18:56 ` hjl at gcc dot gnu dot org 2009-04-10 19:01 ` hjl at gcc dot gnu dot org 2009-04-10 19:36 ` hjl at gcc dot gnu dot org 2009-04-10 19:37 ` hjl dot tools at gmail dot com
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-28301-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).