public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/46336] [C++0X] ICE on invalid: in register_constexpr_fundef, at cp/semantics.c:5571 Date: Thu, 17 Mar 2011 02:36:00 -0000 [thread overview] Message-ID: <bug-46336-4-F25HMlCUpa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-46336-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46336 --- Comment #2 from Jason Merrill <jason at gcc dot gnu.org> 2011-03-17 02:36:15 UTC --- Author: jason Date: Thu Mar 17 02:36:12 2011 New Revision: 171084 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=171084 Log: PR c++/46336 * decl.c (duplicate_decls): Return NULL_TREE for clashing C functions. Added: trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-46336.C Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/decl.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/g++.dg/parse/friend5.C
next prev parent reply other threads:[~2011-03-17 2:36 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-06 23:41 [Bug c++/46336] New: " marc.glisse at normalesup dot org 2010-11-07 11:13 ` [Bug c++/46336] " paolo.carlini at oracle dot com 2011-03-16 21:05 ` jason at gcc dot gnu.org 2011-03-17 2:36 ` jason at gcc dot gnu.org [this message] 2011-03-17 2:40 ` jason at gcc dot gnu.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-46336-4-F25HMlCUpa@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).