This is the mail archive of the
mailing list for the glibc project.
Re: Fourth draft of the Y2038 design document
- From: Andrew Pinski <pinskia at gmail dot com>
- To: Albert ARIBAUD <albert dot aribaud at 3adev dot fr>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Wed, 22 Jun 2016 22:11:20 -0700
- Subject: Re: Fourth draft of the Y2038 design document
- Authentication-results: sourceware.org; auth=none
- References: <20160622005838 dot 60a95c44 dot albert dot aribaud at 3adev dot fr>
On Tue, Jun 21, 2016 at 3:58 PM, Albert ARIBAUD <email@example.com> wrote:
> Hi all,
> I have produced a fourth draft of what will eventually become the Y2038
> design document:
> Relative to the previous draft:
> * the scope clarifies that *only* Y2038 is considered, and no other
> doomsday such as Y2106 or Y9999;
> * all types directly or indirectly derived from time_t are now listed;
> * all APIs using these types are now listed;
> * all functions which use time_t internally are now listed;
> * also listed are types and APIs related to time but which are
> Y2038-safe (even though they might be unsafe for some other
> doomsday, e.g. struct rpc_timeval being Y2106-unsafe).
> As always, comments welcome.
In the aarch64 ILP32 thread, utmp came up as something which needs to
looked into more. Right now utmp struct is stored out in a file and
your specification does not specify how that is going to be handled.
> Albert ARIBAUD