From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id CE6833896C35; Fri, 26 Feb 2021 12:52:37 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org CE6833896C35 From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/99277] C++2a synchronisation is inefficient in GCC 11 and can't be fixed later Date: Fri, 26 Feb 2021 12:52:37 +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: redi at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 11.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: short_desc 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Feb 2021 12:52:37 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D99277 Jonathan Wakely changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[11 Regression] C++2a |C++2a synchronisation is |synchronisation is |inefficient in GCC 11 and |inefficient in GCC 11 and |can't be fixed later |can't be fixed later | --- Comment #3 from Jonathan Wakely --- I already replied on the mailing list. These are inline specifically so we don't tie ourselves to symbols exported from the DSO before the features are stable. They aren't going to be considered stable for GCC 11 so your suggestion is = to disable everything, get no usage experience to help improve it, then at some point re-enable it when it's no more mature than it is now. I don't see how that helps anything. We've done things this way for years. When C++20 support is no longer experimental is when the ABI will be fixed.=