public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paolo dot carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/42338] [c++0x] ICE on decltype usage with templates Date: Thu, 21 Jan 2010 10:17:00 -0000 [thread overview] Message-ID: <20100121101715.27219.qmail@sourceware.org> (raw) In-Reply-To: <bug-42338-18541@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from paolo dot carlini at oracle dot com 2010-01-21 10:17 ------- Thus, Jason, it turns out this is *not* a duplicate of c++/38600, doesn't have to do with mangling template_id_expr, right? By the way, if you have got two spare minutes, could you maybe add something about the latter in that audit trail? Duplicates are coming and coming, I'm afraid people (myself included ;) are a bit confused about why we cannot mangle that. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42338
next prev parent reply other threads:[~2010-01-21 10:17 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-08 23:37 [Bug c++/42338] New: " onay at ee dot bilkent dot edu dot tr 2009-12-09 9:50 ` [Bug c++/42338] " paolo dot carlini at oracle dot com 2009-12-18 0:42 ` redi at gcc dot gnu dot org 2010-01-20 22:42 ` jason at gcc dot gnu dot org 2010-01-21 1:59 ` jason at gcc dot gnu dot org 2010-01-21 10:17 ` paolo dot carlini at oracle dot com [this message] 2010-02-09 22:31 ` jason 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=20100121101715.27219.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).