From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id C607F38708CA; Mon, 15 Jun 2020 12:28:47 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C607F38708CA
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1592224127;
 bh=0KGZdx635E5+yA+hbeoIfhzHkw+gY9qT2/lgaZLNvOg=;
 h=From:To:Subject:Date:In-Reply-To:References:From;
 b=PVqfg21iMwg7b/xNR8LWk0MTl/2fvC8ZlCtlIqCFLyrbrlSPdgurwwDVxl/3iOEV9
 TVxJuxHbv1GJJCHrqq8fCZPG4aA7F5X3iCSlkgvtdewPY93jOjhRXiZqpN+BzlrP34
 2QXO2TNCJ0ontdfeKUgadc8AMGMlFHgbGihkYgOg=
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
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.1.0
X-Bugzilla-Keywords: accepts-invalid, lto, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nathan at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: everconfirmed bug_status cf_reconfirmed_on
Message-ID: <bug-95677-4-erRnTLWyas@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-95677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-95677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <http://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <http://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Jun 2020 12:28:47 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D95677

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 bet=
ween
TUs for '<anon>::x'.  Now we give it a specific name and adjust the linkage=
s of
their contents.=20

The C++ FE should adjust the linkage of '<anon>::x' too.=