From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <musl-return-20766-ml=inbox.vuxu.org@lists.openwall.com>
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-3.0 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS,
	MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H4,
	RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4
Received: from second.openwall.net (second.openwall.net [193.110.157.125])
	by inbox.vuxu.org (Postfix) with SMTP id 2958B20E5E
	for <ml@inbox.vuxu.org>; Tue, 26 Mar 2024 00:30:15 +0100 (CET)
Received: (qmail 8102 invoked by uid 550); 25 Mar 2024 23:25:29 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Reply-To: musl@lists.openwall.com
Received: (qmail 8061 invoked from network); 25 Mar 2024 23:25:29 -0000
Date: Mon, 25 Mar 2024 23:19:29 +0000 (UTC)
From: Thorsten Glaser <tg@mirbsd.de>
X-X-Sender: tg@herc.mirbsd.org
To: musl@lists.openwall.com
In-Reply-To: <UR0Vya1hmBXvuPCcXsD_bEdmjRIYSZ8dbdt3ivdZxfdLASyfvp9ffpD7QPHLad2ZsOGQExkFKdmx6plvq0_eJPhY_PiGHd8Fv1-kUy_ToEg=@pm.me>
Message-ID: <Pine.BSM.4.64L.2403252316420.3887@herc.mirbsd.org>
References: <20240324192258.GY4163@brightrain.aerifal.cx>
 <4YlR0YRqzZlDIOVv6SP8UDoop89n8u7BvQl_7eXNTvDZnogXMxG1z-TLGIBf-O4edUphddXGfADbk_d7Uzb37g5JoH7vOIvvNRMFDxPWZok=@pm.me>
 <RRefgIKYIkNjPM9zuJIzVCjZBi0GC5MnqEYNyLq9Pi2ZquzfwVb6CJSEjDZEd2jMgR0nmf_hoJd4Zl-iMQHW-Qc5K3x9vwt3oskinb1MC58=@pm.me>
 <20240325122113.GB4163@brightrain.aerifal.cx>
 <fc-GwUhx15X7vC5prdjwSO63RHycs6m6PR7qjto8L6ZF8TsSe6mbOmNiJM0X-BuwKPYow9CkGvjDHyfusEtEIfqcueaUbBfC04sAth8a4AM=@pm.me>
 <20240325131318.GD4163@brightrain.aerifal.cx>
 <DOttmdFY87-a4z0bN1aqXHkTKuUqDzsCIyAf0FG9Q9n6KyvPxeThCocJG3R-piziR3eQKONiexvVATdGWjNR3QokLW0ndRHoEEsqegTF-eA=@pm.me>
 <20240325134252.GE4163@brightrain.aerifal.cx> <20240325180208.GF4163@brightrain.aerifal.cx>
 <UR0Vya1hmBXvuPCcXsD_bEdmjRIYSZ8dbdt3ivdZxfdLASyfvp9ffpD7QPHLad2ZsOGQExkFKdmx6plvq0_eJPhY_PiGHd8Fv1-kUy_ToEg=@pm.me>
Content-Language: de-Zsym-DE-1901-u-em-text-rg-denw-tz-utc, en-Zsym-GB-u-cu-eur-em-text-fw-mon-hc-h23-ms-metric-mu-celsius-rg-denw-tz-utc-va-posix
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=utf-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Subject: Re: [musl] Broken mktime calculations when crossing DST boundary

Alexander Weps dixit:

>30th day of the month December was December 31st.

If counting days by counting them from the beginning of the
month, which POSIX is famously not doing even for seconds
since the epoch.

tm_mday is defined as day of month, not days since the
beginning of the month. So 31=CB=A2=E1=B5=97 December always has tm_mday
of 31, independent of whether 30=E1=B5=97=CA=B0 December existed in that
particular month.

bye,
//mirabilos
--=20
=E2=80=9CIt is inappropriate to require that a time represented as
 seconds since the Epoch precisely represent the number of
 seconds between the referenced time and the Epoch.=E2=80=9D
=09-- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2