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 734623858D38; Thu,  7 Sep 2023 17:09:28 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 734623858D38
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1694106568;
	bh=qn9ePHHZYcvS25p+aaqoQ9CFP2MipW8HK0nXh8A4aLo=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=Lo9VvcuSEdfbGxZOcTElUUZB6COgfk/ICEMtLnzrUvgZfl2fnW+2Zu9eME9ckc35E
	 lZvd/ufNYwAgGMwQDZIiBUdi/8janLzKiZUrKSE/LjoC+QCmqmG+yWjktfMR+hS5Pp
	 mhzGKwRct3X+Je0RTDNNYZcIDvdfa3xD1nZO001w=
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/83077] sso-string @ gnu-versioned-namespace.
Date: Thu, 07 Sep 2023 17:09:27 +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: 7.2.0
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: fdumont at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-83077-4-j3q7wpfRgK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83077-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83077-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=3D83077

--- Comment #15 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Iain Sandoe from comment #13)
> (In reply to Iain Sandoe from comment #12)
> > (In reply to Iain Sandoe from comment #11)
> > > (In reply to Fran=C3=A7ois Dumont from comment #10)
> > > > This is because you are facing the PR65762 issue. I just attached a=
 path
> > > > proposal to it that you need to apply too to be able to run your te=
st.
> > > > You'll be even able to simply use --disable-libstdcxx-dual-abi caus=
e I made
> > > > cxx11 abi the default in this case.

> It looks like this was a merge artefact, which I resolved and now it buil=
ds
> - I have some testsuite fails to examine.

With both patches applied (on top of trunk from yesterday) on both Linux and
Darwin I am seeing regressions in the C++ and libstdc++ test suites.  For t=
he
darwin case, I could perhaps have another merge error - but the Linux case =
has
only your two patches and configured with
--enable-symvers=3Dgnu-versioned-namespace (only).

---

many of the libstdc++ fails are of this form:

/home/iains/gcc-master/bld-patched/x86_64-pc-linux-gnu/32/libstdc++-v3/incl=
ude/format:3519:
error: 'std::__format::_Arg_store<_Context, _Args>::_Arg_store(_Tp& ...) [w=
ith
_Tp =3D {const std::chrono::time_point<std::chrono::system_clock,
std::chrono::duration<long long int, std::ratio<60, 1> > >}; _Context =3D
std::basic_format_context<std::__format::_Sink_iter<char>, char>; _Args =3D
{std::basic_format_arg<std::basic_format_context<std::__format::_Sink_iter<=
char>,
char> >::handle}]' is private within this context

many of the c++ fails are of this form:

contracts-tmpl-spec1.C:(.text+0x6f): undefined reference to
`handle_contract_violation(std::experimental::contract_violation const&)'=