PowerPC 64-bit time_t

[Poul-Henning Kamp]

--------
In message <4641.1466766430 at critter.freebsd.dk>, "Poul-Henning Kamp" writes:
>--------
>In message <20160624194454.D1013 at besplex.bde.org>, Bruce Evans writes:
>
>>The only practical option for i386 is to change to unsigned time_t before
>>2038 and hope that i386 goes away before that runs out in 2106.  Changing
>>to uint32_t time_t mainly requires doing something with times before the
>>Epoch.  These are unsupported in POSIX, but are supposed to work back to
>>1902 with int32_t in FreeBSD, except 1 second before the Epoch is the
>>same as the error code (time_t)(-1) so it doesn't work right.
>
>I'd recommend it, dates one timezones worth before epoch are far too
>common in contemporary traffic (particular HTTP).

It's too warm here:  read: I'd recommend *against* it.

>Why don't we make a i387[1] port where time_t is 64 bit and where we jettison
>the museum-ready IBM PC baggage ?
>
>
>[1] Of course a joke reference to floating point HW being mandatory.
>
>-- 
>Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
>phk at FreeBSD.ORG         | TCP/IP since RFC 956
>FreeBSD committer       | BSD since 4.3-tahoe    
>Never attribute to malice what can adequately be explained by incompetence.
>_______________________________________________
>freebsd-arch at freebsd.org mailing list
>https://lists.freebsd.org/mailman/listinfo/freebsd-arch
>To unsubscribe, send any mail to "freebsd-arch-unsubscribe at freebsd.org"
>

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk at FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.