From: Joseph Myers <joseph@codesourcery.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: <libc-alpha@sourceware.org>,
Albert ARIBAUD <albert.aribaud@3adev.fr>,
Y2038 <y2038@lists.linaro.org>
Subject: Re: Fourth draft of the Y2038 design document
Date: Wed, 22 Jun 2016 20:19:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1606222012420.22324@digraph.polyomino.org.uk> (raw)
In-Reply-To: <6204150.Ja8izhmCjv@wuerfel>
On Wed, 22 Jun 2016, Arnd Bergmann wrote:
> We can avoid most of the problems if building with _TIME_BITS=64
> has no effect unless both glibc and the kernel headers are new
> enough to provide the definitions for 64-bit time_t. That way
> we can at least ensure that calling an ioctl command or setsockopt
> with an incompatible ABI will result in an error code rather than
> wrong data.
I'd be a lot more comfortable with requiring new kernel headers to build
and use glibc than with requiring a new kernel at runtime for
_TIME_BITS=64 to work. New kernel headers are one of the easiest things
to use when building glibc, since we have the --with-headers option. (In
fact right now the headers requirement (3.2) is newer than the runtime
requirement (2.6.32) on x86_64 / x86.)
(_TIME_BITS=64 should of course be an OS-independent API, supported for
all glibc configurations. Obviously exactly what Hurd does is up to the
Hurd maintainers, as probably is fixing Hurd to keep it working with
_TIME_BITS=64, but _TIME_BITS=64 should clearly enable 64-bit time_t for
it even if some underlying Y2038-safety is missing. NaCl already has
64-bit time_t so _TIME_BITS=64 would have no effect there.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-06-22 20:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 22:58 Albert ARIBAUD
2016-06-22 11:53 ` Arnd Bergmann
2016-06-22 14:30 ` Joseph Myers
2016-06-22 20:09 ` Arnd Bergmann
2016-06-22 20:19 ` Joseph Myers [this message]
2016-06-23 13:32 ` Arnd Bergmann
2016-06-23 14:33 ` Joseph Myers
2016-06-23 15:34 ` Arnd Bergmann
2016-06-23 16:56 ` Joseph Myers
2016-06-24 13:30 ` Arnd Bergmann
2016-06-29 9:59 ` Albert ARIBAUD
2016-06-29 13:28 ` Arnd Bergmann
2016-07-13 20:40 ` [Y2038] " Deepa Dinamani
2016-07-14 3:16 ` Deepa Dinamani
2016-07-14 11:49 ` Arnd Bergmann
2016-09-07 10:05 ` Albert ARIBAUD
2016-06-29 11:16 ` Albert ARIBAUD
2016-06-29 13:59 ` Arnd Bergmann
2016-09-28 7:18 ` Albert ARIBAUD
2016-09-28 16:38 ` Joseph Myers
2016-06-23 5:11 ` Andrew Pinski
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=alpine.DEB.2.20.1606222012420.22324@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=albert.aribaud@3adev.fr \
--cc=arnd@arndb.de \
--cc=libc-alpha@sourceware.org \
--cc=y2038@lists.linaro.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).