From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 5C58A3858D33; Tue, 28 Feb 2023 13:34:55 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5C58A3858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1677591295; bh=9jL9lQ+MSfkZbBkbldEs8uqXWQmEbcExPo5h3kFXMSs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=URoC+wvxb0uoTx42Sa0oeWT4yfnBupQ/jVMrr5pclJC5Hu7QR0BHTctNyKvNMr+vX TTW7Ek5kG89zEfuvwWz/jStNKxuLBNzRtKdUAO7hqoIxzU6elU2Nf6L9Cqywmuw5vH XvtAt0WGyKACiJK4Bwys8DAgFaz2qGjL1BbQW86U= From: "fw at gcc dot 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:34:55 +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: fw 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: In-Reply-To: References: 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: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108969 --- Comment #6 from Florian Weimer --- (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 Is there anything that prevents these symbol versions getting added for libstdc++.a? I think that could be problematic because a custom DSO typical= ly will not have a version node for GLIBCXX_3.4.31.=