Future of 32 bit time_t?

[Mark Atwood]

Are there any worrisome performance or conformance issues with time64_t on
any of our 32bit targets?

..m

On Mon, Mar 13, 2017 at 5:03 PM Hal Murray <hmurray at megapathdsl.net> wrote:

>
> I have the leap second code mostly cleaned up.  It builds but the tests
> still
> get several errors.  There is no reference to ntpcal_xxx.
>
> The general idea is that the file format uses NTP epoch, but as soon as
> dates
> are read in, they are converted to time_t.  All processing is done using
> time_t.
>
> That works fine now, but will break in 2038.
>
> Is the world going to shift to 64 bit time_t soon enough?  Or should I
> convert everything to time64_t now while the code is somewhat fresh in my
> mind.  Actually, I think I would debug the non64 case first, then update to
> time64_t.
>
>
>
> --
> These are my opinions.  I hate spam.
>
>
>
> _______________________________________________
> devel mailing list
> devel at ntpsec.org
> http://lists.ntpsec.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20170314/15c3067a/attachment.html>