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++/29732] New: [4.0/4.1/4.2/4.3 regression] ICE on invalid friend declaration Date: Sun, 05 Nov 2006 23:13:00 -0000 [thread overview] Message-ID: <bug-29732-1771@http.gcc.gnu.org/bugzilla/> (raw) The following invalid code snippet triggers an ICE since GCC 4.0.0: ================================================= struct A { template<int> template<typename T> friend void foo(T) {} void bar() { foo(0); } }; ================================================= bug.cc: In member function 'void A::bar()': bug.cc:4: internal compiler error: in retrieve_specialization, at cp/pt.c:847 Please submit a full bug report, [etc.] -- Summary: [4.0/4.1/4.2/4.3 regression] ICE on invalid friend declaration Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code, 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=29732
next reply other threads:[~2006-11-05 23:13 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-11-05 23:13 reichelt at gcc dot gnu dot org [this message] 2006-11-05 23:20 ` [Bug c++/29732] " reichelt at gcc dot gnu dot org 2006-11-12 20:39 ` mmitchel at gcc dot gnu dot org 2006-11-26 0:22 ` pinskia at gcc dot gnu dot org 2006-12-07 18:11 ` mmitchel at gcc dot gnu dot org 2006-12-08 6:27 ` mmitchel at gcc dot gnu dot org 2006-12-08 8:10 ` [Bug c++/29732] [4.0/4.1/4.2 " mmitchel at gcc dot gnu dot org 2006-12-10 23:48 ` mmitchel at gcc dot gnu dot org 2006-12-12 1:47 ` mmitchel at gcc dot gnu dot org 2006-12-12 1:53 ` [Bug c++/29732] [4.0 " mmitchel at gcc dot gnu dot org 2007-02-03 20:55 ` gdr 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-29732-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).