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 E58EF3858404; Mon,  8 May 2023 23:06:11 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E58EF3858404
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1683587171;
	bh=ksfqh7rV1YElo3fWgTB8fo7NyVURqrDRX0CmGTNm4f8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=oTKsYWLVP/rYsOldB8JZacMS84PasNnj1+aWkwtFqlmyvmrINfrpk8uWbCXAliFMV
	 79Dewf77+Mdpy3qXLpV+gUz+A/DTQ3oHlvhXHaYI+u+pCLM3HZUAwA4DHagDubPftE
	 bChSvk8P1Zy8tuXZl+UuuYh5E3epeIQTeH9R7WX0=
From: "rodgertq at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/99277] C++2a synchronisation is inefficient in GCC 11
Date: Mon, 08 May 2023 23:06:10 +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: 11.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rodgertq at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 12.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-99277-4-3DxtUCRAYM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-99277-4@http.gcc.gnu.org/bugzilla/>
References: <bug-99277-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=3D99277

--- Comment #23 from Thomas Rodgers <rodgertq at gcc dot gnu.org> ---
(In reply to Thiago Macieira from comment #21)
> I understand that. I don't think it's a reason to repeat the policy, thou=
gh.
>=20
> Anyway, I don't have any new arguments than when we discussed this two ye=
ars
> ago, so I won't pursue this matter further.

(Un)fortunately, the entire implementation detail in the headers will chang=
e,
most likely with GCC14 (ideally moving most of the implementation into the
.so). As Jonathan points out, this hardly the only experimental feature area
within libstdc++ that has undergone such changes.=