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 A6D813858C5E; Tue, 28 Feb 2023 13:54:07 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A6D813858C5E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1677592447;
	bh=Bpu4fKwLF/rt5kUx95AwLAniWAVinhHPwdaUHkPT87c=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=riB9ZhYsrMi+zG4fr6hXDfp0TnAHm/oY2iLUhuDY+J1RwOaLNru3nl9009H9IzKdm
	 LT4r6SW3kJ+pkluYKLs/1rja+69CfrKFWhzU3Abu95PuGsL7QTUfc5MljHPqnD5Dty
	 pJfHwYg1zi9CdWbwEulRhI8hS5/i15Id1vf2K3os=
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/108969] [13 Regression] Initializing iostreams in the
 library needs a GLIBCXX_3.4.31 versioned symbol
Date: Tue, 28 Feb 2023 13:54:07 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 13.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-108969-4-Ts3KAglmwh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-108969-4@http.gcc.gnu.org/bugzilla/>
References: <bug-108969-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
List-Id: <gcc-bugs.sourceware.org>

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

--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Florian Weimer from comment #6)
> (In reply to Jonathan Wakely from comment #2)
> > --- a/libstdc++-v3/src/c++98/globals_io.cc
> > +++ b/libstdc++-v3/src/c++98/globals_io.cc
> > @@ -43,6 +43,12 @@
> >  // In macro form:
> >  // _GLIBCXX_ASM_SYMVER(currentname, oldname, GLIBCXX_3.2)
> >=20=20
> > +#if __has_attribute(symver) && !_GLIBCXX_INLINE_VERSION
> > +# define SYMVER(sym) __attribute__((symver(#sym "@@GLIBCXX_3.4.31")))
> > +#else
> > +# define SYMVER(sym)
> > +#endif
>=20
> Is there anything that prevents these symbol versions getting added for
> libstdc++.a? I think that could be problematic because a custom DSO
> typically will not have a version node for GLIBCXX_3.4.31.

Can we make everything hidden in libstdc++.a?  If somebody builds a DSO
with -static-libstdc++ then he very likely doesn't want to export libstdc++
symbols?=