public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/88264] Support glibc-style tunables for <memory_resource> Date: Mon, 21 Nov 2022 12:44:38 +0000 [thread overview] Message-ID: <bug-88264-4-Dmc45VL68j@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-88264-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88264 --- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> --- This can't be done safely in libstdc++ because we can't call getenv safely. We could be dlopened while another thread is calling setenv. But if that could be solved, other useful tunables would be the filenames to use for chrono::tzdb (for tzdata.zi and leapseconds), and formatting options for the default contract violation handler (e.g. human readable vs log-friendly).
next prev parent reply other threads:[~2022-11-21 12:44 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-88264-4@http.gcc.gnu.org/bugzilla/> 2022-10-11 15:22 ` cvs-commit at gcc dot gnu.org 2022-10-11 15:26 ` redi at gcc dot gnu.org 2022-11-21 12:44 ` redi at gcc dot gnu.org [this message] 2023-12-05 14:30 ` [Bug libstdc++/88264] Support glibc-style tunables for libstdc++ redi 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-88264-4-Dmc45VL68j@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).