[Bug time/34480] mktime fails to determine DST for America/Vancouver from tzdata 2026b

https://sourceware.org/bugzilla/show_bug.cgi?id=3D34480

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fweimer at redhat dot com

--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
(In reply to Aurelien Jarno from comment #0)
> All that said, POSIX 2024 clarifies the mktime behaviour: when tm_isdst is
> 0, the implementation should interpret the input as standard time and not
> attempt to determine if DST is active. Maybe that is the correct fix here.

But what does that actually mean in this context?

America/Vancouver has permanent DST. Does POSIX require that the time_t val=
ue
produced is different for tm_isdst =3D=3D 0 and tm_isdst =3D=3D 1? To avoid=
 producing a
difference, mktime would have to determine whether DST is in effect, I thin=
k.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=