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++/35026] New: [4.3 regression] ICE with parameter pack in pointer type Date: Wed, 30 Jan 2008 01:04:00 -0000 [thread overview] Message-ID: <bug-35026-1771@http.gcc.gnu.org/bugzilla/> (raw) The following invalid code snippet is accepted on mainline: ===================================== template<typename... T> struct A { T* x[1]; }; A<int> a; ===================================== One can also trigger ICEs with the snippet if one compiles it with "-g": bug.cc: In instantiation of 'A<int>': bug.cc:6: instantiated from here bug.cc:2: internal compiler error: in gen_type_die_with_usage, at dwarf2out.c:13432 Please submit a full bug report, [etc.] or with "-gstabs": bug.cc: In instantiation of 'A<int>': bug.cc:6: instantiated from here bug.cc:2: internal compiler error: in dbxout_type, at dbxout.c:2237 Please submit a full bug report, [etc.] -- Summary: [4.3 regression] ICE with parameter pack in pointer type Product: gcc Version: 4.3.0 Status: UNCONFIRMED Keywords: ice-on-invalid-code, accepts-invalid, 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=35026
next reply other threads:[~2008-01-30 0:29 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-01-30 1:04 reichelt at gcc dot gnu dot org [this message] 2008-01-30 1:08 ` [Bug c++/35026] " reichelt at gcc dot gnu dot org 2008-01-30 10:09 ` rguenth at gcc dot gnu dot org 2008-02-14 21:46 ` dgregor at gcc dot gnu dot org 2008-02-15 3:52 ` dgregor at gcc dot gnu dot org 2008-02-15 17:34 ` dgregor at gcc dot gnu dot org 2008-02-15 17:36 ` 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-35026-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).