On Thursday 20 November 2025 20:59:11 LIU Hao wrote: > 在 2025-11-20 20:46, Pali Rohár 写道: > > On Thursday 20 November 2025 14:43:07 Martin Storsjö wrote: > > > On Thu, 20 Nov 2025, Pali Rohár wrote: > > > > > > > This is also _localtime32 function. So another bug in system CRT > > > > library? > > > > > > I don't know - we'd need to extend the printouts in the testcase to see > > > what > > > really is happening here in this case in order to know what really went > > > wrong. > pacific mktime(): 1112520600 sec=0 min=30 hour=1 mday=3 mon=3 year=105 > wday=0 yday=92 isdst=0 > pacific _localtime64(1112520600): sec=0 min=30 hour=1 mday=3 mon=3 year=105 > wday=0 yday=92 isdst=0 > pacific _mktime64(): 1112520600 sec=0 min=30 hour=1 mday=3 mon=3 year=105 > wday=0 yday=92 isdst=0 > pacific _localtime32(1112524200): sec=0 min=30 hour=2 mday=3 mon=3 year=105 > wday=0 yday=92 isdst=1 > Assertion failed: pt_times[i].hour == htm->tm_hour, file > D:/lh_mouse/GitHub/mingw-w64/mingw-w64-crt/testcases/t_time.c, line 172 > > > `pt_times[i].hour` is 3 but `htm->tm_hour` is 2. This is reproducible with > both MSVCRT and UCRT.
I'm somehow not able to trigger this issue. On 64-bit Windows 10 system I'm always getting this line which does not trigger Assertion failed: pacific _localtime32(1112524200): sec=0 min=30 hour=3 mday=3 mon=3 year=105 wday=0 yday=92 isdst=1 This output is from 32-bit crtdll, msvcrt, ucrt and 64-bit msvcrt and ucrt builds. I also tested it on the clean evaluation Windows Server 2022 installation and the output is same, the test is passing. Any idea what I could have missed? _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
