[tz] question about mktime_tzname()

Kees Dekker Kees.Dekker at infor.com
Thu Jan 12 17:06:06 UTC 2017

I will try to check tomorrow. Note that we even don't have 32-bit time_t hosts anymore (since a few years). For me, 64-bit is the only thing to deal with.
Does this patch replace the previous one sent?

-----Original Message-----
From: Paul Eggert [mailto:eggert at cs.ucla.edu] 
Sent: Thursday, January 12, 2017 17:42
To: Arthur David Olson <arthurdavidolson at gmail.com>
Cc: Kees Dekker <Kees.Dekker at infor.com>; Time Zone Mailing List <tz at iana.org>
Subject: Re: [tz] question about mktime_tzname()

On 01/11/2017 02:06 PM, Arthur David Olson wrote:
> > Unfortunately now that I think of it, I see that this can't work on
> > hosts with 32-bit time_t, as they can't cover the 400-year span.  So the
> > code is still broken on 32-bit hosts. Is there a better way to fix
> the code?
> Since 32-bit time_t values can only cover (about) 140 years, not
> covering a 400-year span's not a bug, it's a given.-)

Yes, but unfortunately the code in localtime.c filled in the table only
for the years 1970-2038, and this the 68-year filled-in period was not
enough to make the goback code work correctly (it needs 400 years). I
installed the attached patch to try to fix this; it handles Kees
Dekker's test case correctly on hosts with 32-bit time_t.

More information about the tz mailing list