public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebastian.huber@embedded-brains.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54883] Name mangling of types in an unnamed namespace
Date: Tue, 30 Oct 2012 14:16:00 -0000	[thread overview]
Message-ID: <bug-54883-4-BOePNT3ur6@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

--- Comment #2 from Sebastian Huber <sebastian.huber@embedded-brains.de> 2012-10-30 14:16:05 UTC ---
Known to work GCC 4.0.4, 4.1.2, and 4.2.4:

echo "namespace { enum E { E1 }; } void f(E e) { }" | tee a.c b.c
namespace { enum E { E1 }; } void f(E e) { }
/scratch/install-gcc-4.2.4/bin/g++ -c a.c -o a.o
/scratch/install-gcc-4.2.4/bin/g++ -c b.c -o b.o
nm a.o b.o

a.o:
0000000000000000 T _Z1fN32_GLOBAL__N_a.c_00000000_287815161EE
                 U __gxx_personality_v0

b.o:
0000000000000000 T _Z1fN32_GLOBAL__N_b.c_00000000_BE213B141EE
                 U __gxx_personality_v0

Known to fail 4.3.6, 4.4.7, 4.5.4, 4.6.3, 4.7.2, and 4.8.0.

Is this a bug or a feature?

In the GCC 4.3 release notes there is nothing about namespaces
(http://gcc.gnu.org/gcc-4.3/changes.html).

It would be nice if someone can point out the future direction of this PR, e.g.
NEW or RESOLVED/WONTFIX.


  parent reply	other threads:[~2012-10-30 14:16 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 [this message]
2012-12-09  2:50 ` [Bug c++/54883] [4.6/4.7/4.8 Regression] " pinskia at gcc dot gnu.org
2012-12-11 21:32 ` 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-BOePNT3ur6@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: link
Be 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).