https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276281
--- Comment #8 from Warner Losh <i...@freebsd.org> --- (In reply to Ken McDonell from comment #7) So a couple of things on my 14.0-RC2 machine and a 15.0-current (jan 10th): % env TZ=AEST-10AEDT-11,M10.5.0,M3.5.0 date -r 1044144000 Sun Feb 2 11:00:00 AEDT 2003 So that looks right. That eliminates at least the parsing code from being the problem. A similar test on a linux box gives: % env TZ=AEST-10AEDT-11,M10.5.0,M3.5.0 date --date='@1044144000' Sun Feb 2 11:00:00 AEDT 2003 But then I run your reproducer test against 14.0-RC2 and I get: % ./foo OK I am: FreeBSD 14.0-RC2 #0 releng/14.0-n265367-7bdb67cb1cfe: Thu Oct 26 17:30:50 MDT 2023 imp@zooty:/usr/home/imp/obj/usr/home/imp/git/releng-14.0/amd64.amd64/sys/GENERIC 14.0-RC2 and % /foo OK I am: FreeBSD 15.0-CURRENT #58 main-n267479-18469e00dc45-dirty: Wed Jan 10 16:31:01 MST 2024 imp@rebo:/usr/home/imp/obj/usr/home/imp/git/head/amd64.amd64/sys/GENERIC 15.0-CURRENT So now I'm confused. I hate 'works for me' bugs... I wonder how your system may differ from mine? Granted, none of these are exactly 14.0, but I'd expect if it worked in 14.0-RC2 but not in 14.0 release p3, I'd expect 15.0 also to be bad as well... Especially since I don't see any 14.0 time changes since the release (the last one being April 26th, 2023, well predating my RC2 system. So I'd like to find out why your system is different, but I'm unsure the best way to do that. The only thing I can think of is architecture. What architecture are you running this on? All my tests are amd64. Did I see an i386 in there somewhere? -- You are receiving this mail because: You are the assignee for the bug.
