From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 42BA13858D33; Mon, 6 Nov 2023 10:00:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 42BA13858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1699264846; bh=wt3v3uEPQ/V5sS6JUO1LxzMxhGKhEo1PGCUzjlxK90w=; h=From:To:Subject:Date:In-Reply-To:References:From; b=uT30jkt1Hli4SGN4Oa8YI6rATi8thY2kVN2lcigE7nWKiEIJX6T5Wpbn315PDRNQc sMrny02sSwBGdCDaM+yTfUPB0pFcvOB4bq5wbFF0OH6F+i3zM8HdD9/SJjMHgPRa2A lxp//TlYt2Zvjj/GhiPuXh5Po3Lfw96CnABP57SM= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/112351] libstdc++ locale init doesn't handle __gthread_once failure Date: Mon, 06 Nov 2023 10:00:45 +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.2.1 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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=3D112351 --- Comment #1 from Richard Biener --- The question is also how much of explicit thread safety is needed when the = init is now happening inside libstdc++ (thus from _init which should be already ensured to execute exactly once)? Is that (_init time) done for all targets/configurations btw?=