zdump on 64bit architectures being worked on?

[Stuart Bishop]

On Wed, Oct 8, 2008 at 11:32 PM, Olson, Arthur David (NIH/NCI) [E]
<olsona at dc37a.nci.nih.gov> wrote:
> As far as I know, zdump is working on 64-bit systems. Do note that time_t structures typically contain "year" elements that are less than 64 bits wide; when this is the case, very very negative and very very positive time_t values are associated with years that can't be represented using time_t's; this is why zdump shows "NULL" for these values.

I think I see.  For my use, I think I should just be ignoring the
first two and last two lines of zdump -v output (I'm using it to
generate all the transition points from a known good implementation to
check against my implementation).  I'm not sure if they contain
meaningful information for other use cases.

Under i386 I get this:

Africa/Abidjan Fri Dec 13 20:45:52 1901 UTC = Fri Dec 13 20:29:44 1901
LMT isdst=0 gmtoff=-968
Africa/Abidjan Sat Dec 14 20:45:52 1901 UTC = Sat Dec 14 20:29:44 1901
LMT isdst=0 gmtoff=-968
Africa/Abidjan Mon Jan 1 00:16:07 1912 UTC = Sun Dec 31 23:59:59 1911
LMT isdst=0 gmtoff=-968
Africa/Abidjan Mon Jan 1 00:16:08 1912 UTC = Mon Jan 1 00:16:08 1912
GMT isdst=0 gmtoff=0
Africa/Abidjan Mon Jan 18 03:14:07 2038 UTC = Mon Jan 18 03:14:07 2038
GMT isdst=0 gmtoff=0
Africa/Abidjan Tue Jan 19 03:14:07 2038 UTC = Tue Jan 19 03:14:07 2038
GMT isdst=0 gmtoff=0

Under 64 bit I get the following:

Africa/Abidjan -9223372036854775808 = NULL
Africa/Abidjan -9223372036854689408 = NULL
Africa/Abidjan Mon Jan 1 00:16:07 1912 UTC = Sun Dec 31 23:59:59 1911
LMT isdst=0
Africa/Abidjan Mon Jan 1 00:16:08 1912 UTC = Mon Jan 1 00:16:08 1912 GMT isdst=0
Africa/Abidjan 9223372036854689407 = NULL
Africa/Abidjan 9223372036854775807 = NULL


-- 
Stuart Bishop <stuart at stuartbishop.net>
http://www.stuartbishop.net/