From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, 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 5393E22718 for ; Sun, 24 Mar 2024 20:06:19 +0100 (CET) Received: (qmail 27936 invoked by uid 550); 24 Mar 2024 19:01:36 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 27901 invoked from network); 24 Mar 2024 19:01:35 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pm.me; s=protonmail3; t=1711307166; x=1711566366; bh=hMDrYMtn21KqwQug3pZABS10upH2eoxJU06OIohkLjg=; h=Date:To:From:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=sJ8QyGZvTHKvsMzKZ1hqrdj3MPh1HmxPza98PH3X6agoXcn6P8kRZjvkzBrOA43YL 7empkW6vZlBAzGZxaRTX8wGzbVcDhEJviic53+KVfJUtcp6pLS5Wocf2SbQJ9RJMZD uhpm+n0y3OFCXlRF9GUJXYGXP8pk8QdB1J2LoO3txO8sPHQ2ew6vQLGHszKItVPfpE 8v/s8lZSbZgIFfW2+6Zb1vW7PO/r2RDTLysPsPfR4LGgryK6srr7yoQyOK3kqJRN08 veLSIguXKZ8hhtk2ZOzKJPY8otx3lVM4TgI1CP0TpX9G/7ONAAHOpu2EpgiGOqdu/d t5qtNPs6KED4g== Date: Sun, 24 Mar 2024 19:05:54 +0000 To: musl@lists.openwall.com From: Alexander Weps Message-ID: In-Reply-To: <20240324200122.8feda8341011587ec6cccf61@zhasha.com> References: <20240324170436.GV4163@brightrain.aerifal.cx> <0_9-JV2MW3avVvzhE9vjqKqCX0fEZy0uUuZKIohFGEFDBY912nwZyxZe560H0cf_b8L2gD8e0eUAUp2Q3e1rmra3XEppx9HPhhFeulwLYZA=@pm.me> <20240324180200.GW4163@brightrain.aerifal.cx> <20240324182458.GX4163@brightrain.aerifal.cx> <9c2qfe36CoPBfKjzn1lDDZ_hfyNJCZW6-6ZTZlQgHAPr2djicIMMweEqUoQoQsDWsBt4AAZBL8vZlcsVCL950rYhcPpMDvhzDWean3oVHbs=@pm.me> <20240324200122.8feda8341011587ec6cccf61@zhasha.com> Feedback-ID: 20507743:user:proton 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 Provide struct tm that was passed as an argument. AW On Sunday, March 24th, 2024 at 20:01, Joakim Sindholt wrote: > On Sun, 24 Mar 2024 18:36:40 +0000, Alexander Weps exander77@pm.me wrote: > > > But there cannot be a case where you have normalized time add > > something, normalize and create normalized time that is lower and vice > > versa. > > > I'm curious. How do you imagine mktime, which takes only 1 parameter and > has no memory, deduces that to get the presently invalid 02:00:00 > timestamp it's looking at you added 1 second to a valid 01:59:59 > timestamp rather than say, subtracting 1 hour from a valid 03:00:00 > timestamp?