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++/34103] New: [4.3 regression] ICE with invalid variadic template functions Date: Thu, 15 Nov 2007 07:54:00 -0000 [thread overview] Message-ID: <bug-34103-1771@http.gcc.gnu.org/bugzilla/> (raw) The following invalid testcase triggers an ICE on mainline: ============================================================ template<typename> struct A {}; template<typename...T> void foo(A<T>, A<T>); template<typename...T> void foo(A<T>, A<T>) {} ============================================================ bug.cc:3: error: parameter packs not expanded with `...': bug.cc:3: note: 'T' bug.cc:5: error: parameter packs not expanded with `...': bug.cc:5: note: 'T' bug.cc:5: internal compiler error: canonical types differ for identical types A<<expression error> > and A<<expression error> > Please submit a full bug report, [etc.] The bug appeared between 2007-11-03 and 2007-11-06. -- Summary: [4.3 regression] ICE with invalid variadic template functions Product: gcc Version: 4.3.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=34103
next reply other threads:[~2007-11-15 7:54 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-11-15 7:54 reichelt at gcc dot gnu dot org [this message] 2007-11-15 7:54 ` [Bug c++/34103] " reichelt at gcc dot gnu dot org 2007-11-19 5:21 ` pinskia at gcc dot gnu dot org 2007-11-27 21:58 ` mmitchel at gcc dot gnu dot org 2007-11-27 22:09 ` pinskia at gcc dot gnu dot org 2007-11-27 22:16 ` mmitchel at gcc dot gnu dot org 2007-12-20 21:04 ` dgregor at gcc dot gnu dot org 2008-01-15 17:56 ` dgregor at gcc dot gnu dot org 2008-01-15 18:50 ` dgregor at gcc dot gnu dot org 2008-01-15 18:52 ` dgregor at gcc dot gnu dot org 2008-01-16 12:30 ` ubizjak at gmail dot com 2008-01-16 13:27 ` dgregor at gcc dot gnu dot org 2008-01-16 13:29 ` rguenth at gcc dot gnu dot org 2008-01-16 14:02 ` ubizjak at gmail dot com 2008-01-16 16:01 ` pinskia at gcc dot gnu dot org 2008-01-19 20:10 ` danglin at gcc dot gnu dot org 2008-01-19 20:13 ` dave at hiauly1 dot hia dot nrc dot ca 2008-01-28 10:07 ` dominiq at lps dot ens dot fr 2008-01-28 21:53 ` dgregor at gcc dot gnu dot org 2008-01-29 14:02 ` dgregor at gcc dot gnu dot org 2008-01-29 14:26 ` dgregor 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-34103-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).