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 57CE03858C30; Mon,  8 May 2023 15:15:35 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 57CE03858C30
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1683558935;
	bh=7er1RRd73/xIIytxX1XWBX7+e1VkiSbRRCCK9Cz8U7o=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=uw5OuDlM0Vwil32kSZp6Kl1yvAnQ13sm2aEa4WuyPkvvfDbzDDyXeGufVG4ZR7WaF
	 3AkfxQ7P4xUzmRrMIEE6AQOEvblmBKDnQTSvHBmdGHTVAKakIQLgK2YSbF3als78x2
	 lVxIRpPjUaShtUFgRQldkx4KOCURv+S6lPCc1C04=
From: "thiago at kde dot 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 15:15:34 +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: thiago at kde dot 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.4
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: resolution bug_status
Message-ID: <bug-99277-4-SR8uSAMZTJ@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

Thiago Macieira <thiago at kde dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #13 from Thiago Macieira <thiago at kde dot org> ---
I believe this was fixed before release. Just the issue not closed.=