public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/31903] unwanted anonymous namespacing linkage
Date: Fri, 11 May 2007 21:55:00 -0000 [thread overview]
Message-ID: <20070511215544.28490.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31903-1447@http.gcc.gnu.org/bugzilla/>
------- Comment #4 from pinskia at gcc dot gnu dot org 2007-05-11 22:55 -------
(In reply to comment #3)
> I think this is a bug on Linux as well, though, I suspect it don't fail to
> build, but rather I think it will compare the two typeinfo objects as equal
> even though they are unrelated to each other.
Nope:
Y:
.long _ZTIN33_GLOBAL__N_t.cc_00000000_E25ADE893fooE
X:
.long _ZTIN33_GLOBAL__N_t.cc_00000000_1F13DE273fooE
So the typeinfo are different.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31903
next prev parent reply other threads:[~2007-05-11 21:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 21:15 [Bug c++/31903] New: " mrs at apple dot com
2007-05-11 21:20 ` [Bug target/31903] " pinskia at gcc dot gnu dot org
2007-05-11 21:25 ` pinskia at gcc dot gnu dot org
2007-05-11 21:45 ` mrs at apple dot com
2007-05-11 21:55 ` pinskia at gcc dot gnu dot org [this message]
2007-05-11 23:01 ` mrs at apple dot com
2007-05-12 0:00 ` sabre at nondot dot org
2007-05-12 13:16 ` pinskia at gcc dot gnu dot org
2007-05-12 13:31 ` [Bug c++/31903] [4.3 Regression] " pinskia at gcc dot gnu dot org
2007-05-13 22:18 ` geoffk at gcc dot gnu dot org
2007-06-13 22:31 ` [Bug c++/31903] [4.3 Regression] typeinfo of classes in anon namespace isn't being marked static geoffk at gcc dot gnu dot org
2007-06-14 21:11 ` geoffk 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=20070511215544.28490.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: 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).