public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/54883] [4.6/4.7/4.8 Regression] Name mangling of types in an unnamed namespace Date: Sun, 09 Dec 2012 02:50:00 -0000 [thread overview] Message-ID: <bug-54883-4-DnJzflHt7o@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54883-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54883 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |ABI Status|UNCONFIRMED |NEW Last reconfirmed| |2012-12-09 Known to work| |4.2.4 Target Milestone|--- |4.6.4 Summary|Name mangling of types in |[4.6/4.7/4.8 Regression] |an unnamed namespace |Name mangling of types in | |an unnamed namespace Ever Confirmed|0 |1 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-12-09 02:50:00 UTC --- Confirmed. Simple linktime testcase: echo "namespace { enum E { E1 }; } void f(E e) { }" | tee a.c b.c > /dev/null echo "int main(void){}"> c.c g++ a.c b.c c.c
next prev parent reply other threads:[~2012-12-09 2:50 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-10 7:08 [Bug c++/54883] New: " wolfgang.roehrl@gi-de.com 2012-10-10 8:50 ` [Bug c++/54883] " paolo.carlini at oracle dot com 2012-10-26 13:49 ` sebastian.huber@embedded-brains.de 2012-10-30 14:16 ` sebastian.huber@embedded-brains.de 2012-12-09 2:50 ` pinskia at gcc dot gnu.org [this message] 2012-12-11 21:32 ` [Bug c++/54883] [4.6/4.7/4.8 Regression] " jason at gcc dot gnu.org 2012-12-11 22:46 ` jason at gcc dot gnu.org 2012-12-11 22:47 ` jason at gcc dot gnu.org 2012-12-11 22:47 ` jason at gcc dot gnu.org 2012-12-11 22:48 ` 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-54883-4-DnJzflHt7o@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).