public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95677] undefined reference to `(anonymous namespace)::xx'
Date: Mon, 15 Jun 2020 12:28:47 +0000 [thread overview]
Message-ID: <bug-95677-4-erRnTLWyas@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95677-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95677
Nathan Sidwell <nathan at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-06-15
--- Comment #6 from Nathan Sidwell <nathan at gcc dot gnu.org> ---
Ah, anonymous namespaces have internal linkage (and a program-wide unique
identifier). Their contents have the linkage they have. but because they're
within the anonumous namespace they cannot be named from elsewhere, so they
have internal linkage for implementation purposes.
when we actually gave anonymous namespaces there would be no collisions between
TUs for '<anon>::x'. Now we give it a specific name and adjust the linkages of
their contents.
The C++ FE should adjust the linkage of '<anon>::x' too.
next prev parent reply other threads:[~2020-06-15 12:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 8:00 [Bug lto/95677] New: " sujian.liu at huawei dot com
2020-06-15 8:12 ` [Bug c++/95677] " rguenth at gcc dot gnu.org
2020-06-15 8:36 ` sujian.liu at huawei dot com
2020-06-15 12:02 ` nathan at gcc dot gnu.org
2020-06-15 12:05 ` rguenth at gcc dot gnu.org
2020-06-15 12:07 ` rguenth at gcc dot gnu.org
2020-06-15 12:28 ` nathan at gcc dot gnu.org [this message]
2020-06-18 7:34 ` sujian.liu at huawei dot com
2020-07-15 1:40 ` sujian.liu at huawei dot com
2020-09-16 8:11 ` sujian.liu at huawei dot com
2020-09-23 17:41 ` nathan at gcc dot gnu.org
2020-10-07 14:35 ` nathan 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-95677-4-erRnTLWyas@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).