public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.aribaud@3adev.fr>
To: GNU C Library <libc-alpha@sourceware.org>
Subject: Y2038: seventh draft of the design document and 1st WIP branch
Date: Wed, 21 Jun 2017 10:22:00 -0000	[thread overview]
Message-ID: <20170420152051.568f2050.albert.aribaud@3adev.fr> (raw)
Message-ID: <20170621102200.mT3mFlLP4BiacFfu-QGgZbFbyAE2fYa9AZ1XfM6dQ8Q@z> (raw)

Hi all,

I have produced a seventh draft of the Y2038 design document:

https://sourceware.org/glibc/wiki/Y2038ProofnessDesign?rev=153

Relative to the previous draft (to which there were no comments
apparently):

 * Some precisions were added regarding implementation types

 * The location of a WIP implementation branch is provided  

As always, comments welcome on the document.

Regarding the branch, should I post it here as an [RFC] patch series?
Right now, I'm thinking it is not complete enough for a usual RFC,
but I need feedback to know what is in the right direction and what is
not.

For the moment, the branch only targets ARM, not all APIs are
implemented, and some (the stat family) are WIP because at the moment
there are no kernel patches available to provide Y2038-proof stat
syscalls, so the impelmentations skip the "try the 64-bit-time
syscalls if available" part and skip straight to the "fallback to
32-bit, non-Y2038-proof, syscalls" part.

Note: I have created a framework to test the branch, available at
https://github.com/3adev/y2038. It builds tests for an ARM
architecture and runs them in a QEMU ARM system containing a
Y2038-patched kernel, the Y2038 GLIBC WIP branch, a busybox-based
minimal root fs and system, and ad hoc test applications (one built
with -DTIME_BITS=64, one without, for comparison). This too is WIP, as
it progresses alongside the GLIBC branch.

Thanks in advance for your feedback.

Cordialement,
Albert ARIBAUD
3ADEV

             reply	other threads:[~2017-06-21 10:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-20 13:20 Albert ARIBAUD [this message]
2017-06-21 10:22 ` Albert ARIBAUD
2018-11-15 14:04 ` Sixth draft of the Y2038 design document Dmitry V. Levin
2018-11-15 14:39   ` Arnd Bergmann
2018-11-15 15:30     ` extending wait4(2) or waitid(2) linux syscall Dmitry V. Levin
2018-11-15 15:38       ` hpa
2018-11-16  7:14         ` Arnd Bergmann
2018-11-16 10:27           ` Florian Weimer
2018-11-16 15:17             ` Arnd Bergmann
2018-11-16 16:03               ` Paul Eggert
2018-11-16 18:46           ` hpa
2018-11-16 18:48           ` hpa
2018-11-16  7:13       ` Arnd Bergmann
2018-11-16 12:42       ` Dave Martin
2018-11-16 13:40         ` Florian Weimer
2018-11-16 14:26           ` Dave Martin
2018-11-17  1:50       ` Arnd Bergmann
2018-11-26 15:18         ` Florian Weimer
2018-11-26 17:15           ` Arnd Bergmann
2018-11-26 17:27             ` Daniel Colascione
2018-11-28  9:31             ` Florian Weimer
2018-11-28  9:37               ` Christian Brauner
2018-11-28  9:41                 ` Florian Weimer
2018-11-28 18:50                   ` Daniel Colascione
2018-11-15 18:25     ` Sixth draft of the Y2038 design document hpa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170420152051.568f2050.albert.aribaud@3adev.fr \
    --to=albert.aribaud@3adev.fr \
    --cc=libc-alpha@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).