public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/34056] [4.3 regression] ICE with parameter pack and pointer Date: Tue, 13 Nov 2007 12:12:00 -0000 [thread overview] Message-ID: <20071113121210.6604.qmail@sourceware.org> (raw) In-Reply-To: <bug-34056-1771@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from jakub at gcc dot gnu dot org 2007-11-13 12:12 ------- The set_packs_to_error stuff is very problematic in this case, because trees are shared and the C++ FE certainly doesn't expect error_mark_nodes to appear at random places. In this case T* type is shared (as the pointer to T has been cached). check_for_bare_parameter_packs should have errored about this twice, but will do only once because of the sharing and in the second case just won't fail, so doesn't let the caller to deal with the errorneous type. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34056
next prev parent reply other threads:[~2007-11-13 12:12 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-11-10 19:57 [Bug c++/34056] New: " reichelt at gcc dot gnu dot org 2007-11-10 19:57 ` [Bug c++/34056] " reichelt at gcc dot gnu dot org 2007-11-13 12:12 ` jakub at gcc dot gnu dot org [this message] 2007-11-13 13:44 ` jakub at gcc dot gnu dot org 2007-11-13 18:28 ` jakub at gcc dot gnu dot org 2007-11-13 18:28 ` jakub 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=20071113121210.6604.qmail@sourceware.org \ --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).