From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id F0E59386F440; Tue, 9 Apr 2024 23:50:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F0E59386F440 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1712706628; bh=6Dw0Hs1ONuW0VWToFQaywAJ+lVfx2YoC/RwLeyNy9Ns=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ohW0DxX8dsBiZSoEh9YH6sT3XusFZ6rFrOI9z4+koNq9Bs73+3axV/ECiCpsGJMAv 8cic1RW2lRxjDkqlG6x6cxNsqr+Ix0e1Q7fbwWFXGa7JB5gpulj2jYXRGZknz1CxMn KDG7XmtgsUkzyE+iw3swYOEusgXBlQaG2pnMkUP0= From: "harald at gigawatt dot nl" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/114645] std::chrono::current_zone ignores $TZ on Linux Date: Tue, 09 Apr 2024 23:50:28 +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: harald at gigawatt dot nl X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WONTFIX 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 #18 from Harald van Dijk --- (In reply to Jonathan Wakely from comment #16) > ... incorrectly though? Given that you have expressed your view that *any* attempt at using TZ is inherently incorrect, I am not surprised that you view libc++'s attempt as incorrect. :) I am not intending to get involved in discussion of what the correct behavi= our is, I merely wanted to correct the record about what other implementations = do.=