From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 73CCE3854577; Mon, 21 Nov 2022 12:44:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 73CCE3854577 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1669034680; bh=VeyZEiXJb05XWJbU0fBk8A8bqjr3Ny2gWfyBHG0KRnQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=GSh2YYDpEU24cu/RbYnyH4PXI2d3J19AT911GZ9d0V0Nn0HbjBXVyefIqVBsR/pWL GnHR+lQNTpskb1sQutBkOkgKNIHvKcpFfsldfHlKir/cLIeBvfuJdD8/CNeTJPTEyL KtSbW3AQJdG2UzqT34gThGlan8BbP0HKi49ZClXo= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/88264] Support glibc-style tunables for Date: Mon, 21 Nov 2022 12:44:38 +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: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: redi 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=3D88264 --- Comment #6 from Jonathan Wakely --- 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).=