public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/112351] libstdc++ locale init doesn't handle __gthread_once failure Date: Tue, 07 Nov 2023 12:55:59 +0000 [thread overview] Message-ID: <bug-112351-4-WhJOaKWQfN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112351-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112351 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:7562f089a190953b8ef615b90b7b0520e812a930 commit r14-5220-g7562f089a190953b8ef615b90b7b0520e812a930 Author: Richard Biener <rguenther@suse.de> Date: Mon Nov 6 11:31:40 2023 +0100 libstdc++/112351 - deal with __gthread_once failure during locale init The following makes the C++98 locale init path follow the way the C++11 performs initialization. This way we deal with pthread_once failing, falling back to non-threadsafe initialization which, given we initialize from the library, should be serialized by the dynamic loader already. PR libstdc++/112351 libstdc++-v3/ * src/c++98/locale.cc (locale::facet::_S_initialize_once): Check whether _S_c_locale is already initialized. (locale::facet::_S_get_c_locale): Always perform non-threadsafe init when threadsafe init failed.
next prev parent reply other threads:[~2023-11-07 12:56 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-02 15:07 [Bug libstdc++/112351] New: " rguenth at gcc dot gnu.org 2023-11-02 15:48 ` [Bug libstdc++/112351] " redi at gcc dot gnu.org 2023-11-06 10:00 ` rguenth at gcc dot gnu.org 2023-11-06 10:47 ` redi at gcc dot gnu.org 2023-11-07 12:55 ` cvs-commit at gcc dot gnu.org [this message] 2023-11-07 12:57 ` rguenth at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-112351-4-WhJOaKWQfN@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).