Yo Eric! On Tue, 18 Apr 2017 16:38:00 -0400 "Eric S. Raymond" <e...@thyrsus.com> wrote:
> Gary E. Miller <g...@rellim.com>:
> > The 32-bit problem is that you have to deal with timespec(32)
> > for system time. That breaks in 2038. When we read system time
> > in timespec(32) we do not know if the currennt year is 1971 or
> > 2039.
>
> The integral part of timespec is time_t which has been 64-bit *even
> on 32-bit Linuxes* for, what is it, close to 20 years now?
>
> I am prepared to assume that by 2038 we will be able to put in a
> config test that barfs on 32-bit time_t without causing a ripple.
Gentoo 32 bit uses timespec(64). But not all distros do, and POSIX does
not mandate it. POSIX just says time_t is a signed integer.
FreeBSD 8 defines time_t as int32_t.
QNX 6 also hass 32 bit time_t.
I'm happy to EOL any OS that still uses 32 bit time_t. If we do so we
just need to be explicit about it. Then we have no remaining 32 bit
only problems.
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can’t measure it, you can’t improve it." - Lord Kelvin
pgph6e0bjgeSl.pgp
Description: OpenPGP digital signature
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
