From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A995E385842C; Mon, 8 Apr 2024 20:23:12 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A995E385842C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1712607792; bh=8TMVBRWyplH0S2bafMGDJ69uL2ouPkJ0GTRJdXxxtbU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=G5C3DSZfcmRSsXvP3K6OjvLiiOJUutY+lDbThQqHeyoQiaHIMu4O0VVtzSnhIfVUk FnJttbcFTJg9yuTq0+7/KqEScbmWS0d06DEaVECYHKBKvHg/KuxTUAt1edSaDT0Uku 6cERSyP1o+CWrPA00P1x0Ykr1zrN2Jx0OM79yTd8= From: "hristo at venev dot name" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/114645] std::chrono::current_zone ignores $TZ on Linux Date: Mon, 08 Apr 2024 20:23:12 +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: hristo at venev dot name X-Bugzilla-Status: UNCONFIRMED 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=3D114645 --- Comment #2 from Hristo Venev --- That makes current_zone() quite a bit completely useless and means that practically every use of current_zone() is most likely a bug. Is there some way to get the timezone libc would consider local?=