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++/27667] New: [4.0/4.1/4.2 regression] ICE with in-class specialization Date: Thu, 18 May 2006 19:31:00 -0000 [thread overview] Message-ID: <bug-27667-1771@http.gcc.gnu.org/bugzilla/> (raw) The following invalid code snippet triggers an ICE since GCC 3.4.5 / 4.0.3: ======================================= struct A { template<int> static void foo () {} template<> static void foo<0>() {} }; ======================================= bug.cc:4: error: explicit specialization in non-namespace scope 'struct A' bug.cc:4: internal compiler error: in poplevel, at cp/decl.c:551 Please submit a full bug report, [etc.] -- Summary: [4.0/4.1/4.2 regression] ICE with in-class 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=27667
next reply other threads:[~2006-05-18 19:31 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-05-18 19:31 reichelt at gcc dot gnu dot org [this message] 2006-05-18 21:36 ` [Bug c++/27667] " pinskia at gcc dot gnu dot org 2006-05-26 15:07 ` bangerth at dealii dot org 2006-06-04 19:14 ` mmitchel at gcc dot gnu dot org 2006-07-17 3:24 ` mmitchel at gcc dot gnu dot org 2006-09-23 16:19 ` lmillward at gcc dot gnu dot org 2006-09-23 16:20 ` patchapp at dberlin dot org 2006-09-25 19:58 ` lmillward at gcc dot gnu dot org 2006-09-25 19:59 ` [Bug c++/27667] [4.0/4.1 " lmillward at gcc dot gnu dot org 2007-02-03 17:04 ` gdr at gcc dot gnu dot org 2007-02-03 20:32 ` pinskia at gcc dot gnu dot org 2007-02-14 9:40 ` mmitchel at gcc dot gnu dot org 2008-07-04 15:32 ` [Bug c++/27667] [4.1 " jsm28 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-27667-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).