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++/63942] [5.0 Regression] constexpr conflicts with previous declaration Date: Mon, 24 Nov 2014 12:49:00 -0000 [thread overview] Message-ID: <bug-63942-4-bpIDhmKHQF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63942-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63942 --- Comment #13 from Jason Merrill <jason at gcc dot gnu.org> --- Author: jason Date: Mon Nov 24 12:49:08 2014 New Revision: 218016 URL: https://gcc.gnu.org/viewcvs?rev=218016&root=gcc&view=rev Log: PR c++/63942 * mangle.c (mangle_decl): If we aren't going to create a symbol alias, don't build the alias DECL either. Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/mangle.c
prev parent reply other threads:[~2014-11-24 12:49 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-18 18:28 [Bug libstdc++/63942] New: " dje at gcc dot gnu.org 2014-11-19 9:52 ` [Bug libstdc++/63942] " redi at gcc dot gnu.org 2014-11-19 9:55 ` [Bug c++/63942] " rguenth at gcc dot gnu.org 2014-11-19 16:58 ` dje at gcc dot gnu.org 2014-11-19 17:03 ` dje at gcc dot gnu.org 2014-11-19 17:08 ` dje at gcc dot gnu.org 2014-11-20 4:15 ` jason at gcc dot gnu.org 2014-11-20 13:55 ` dje at gcc dot gnu.org 2014-11-21 13:25 ` jason at gcc dot gnu.org 2014-11-21 14:23 ` dje at gcc dot gnu.org 2014-11-21 15:38 ` jason at gcc dot gnu.org 2014-11-21 16:17 ` jason at gcc dot gnu.org 2014-11-21 21:35 ` jason at gcc dot gnu.org 2014-11-21 21:38 ` jason at gcc dot gnu.org 2014-11-24 12:49 ` jason at gcc dot gnu.org [this message]
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-63942-4-bpIDhmKHQF@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).