From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id F0CD73858C31; Fri,  8 Mar 2024 07:59:06 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org F0CD73858C31
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1709884746;
	bh=ABlylLhAjMOL/Pzn6JhdEn8YvdUhwsIDHk3YHZlNZaI=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=OB1JQV7JcSQ6I+kaP84dmBUdg1EcnUGaaPXZLyXtvyiB3Vs96UXYqv+OG7PBepLLf
	 Gt6uAAL2LzzvhICYkvAUz4aKALC15P04c48hqAnpiC6HXDNjGmUls7metcf2xpynds
	 J+TRfI4KtplFhgqQBWJwwWlIKigvS7lsxLlxm8oI=
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/114279] utc_clock does not support leap seconds
Date: Fri, 08 Mar 2024 07:59:06 +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: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
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: <bug-114279-4-CcREQC22mw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114279-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114279-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D114279

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
It certainly does take leap seconds into account, as demonstrated by the ou=
tput
example below the text you quoted, which is reproduced in the testsuite:

https://gcc.gnu.org/git/?p=3Dgcc.git;a=3Dblob;f=3Dlibstdc%2B%2B-v3/testsuit=
e/std/time/clock/utc/io.cc;h=3D55c53dc4057fe90b8a0f7192cc38ffe313f5afd4;hb=
=3DHEAD

And also:

https://gcc.gnu.org/git/?p=3Dgcc.git;a=3Dblob;f=3Dlibstdc%2B%2B-v3/testsuit=
e/std/time/clock/utc/leap_second_info.cc;h=3D2fabda494234a48dc2920e291f5a92=
a8fe1d02fa;hb=3DHEAD

This seems to be just a bug in the from_stream overload, not utc_clock.=