public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Albert ARIBAUD (3ADEV)" <albert.aribaud@3adev.fr>
To: libc-alpha@sourceware.org
Cc: "Albert ARIBAUD (3ADEV)" <albert.aribaud@3adev.fr>
Subject: [PATCH v3 0/2] Y2038 support batch 1 - __time64_t and __tz_convert
Date: Sat, 16 Jun 2018 17:13:00 -0000	[thread overview]
Message-ID: <20180616171331.25224-1-albert.aribaud@3adev.fr> (raw)

This is the first batch of Y2038 support patches.

The first patch introduces __TIMESIZE (which is the bit size of time_t
at glibc build time, and equals __WORDSIZE except for x32 where __WORDSIZE
is 32 but __TIMESIZE is 64) and __time64_t, the 64-bit counterpart of time_t,
to be used in 64-bit-time implementations of public APIs related to time.
Note that __time64_t replaces internal_time_t previously introduced.

The second patch makes __tz_convert compatible with 64-bit time. This
implies creating 64-bit-time versions of its callers and turning their
original versions into wrappers if they were 32-bit-time.

These patches are functionally tested as part of the whole Y2038 patch
series using the ad hoc framework at https://github.com/3adev/y2038 which
runs tests using times below, at and beyond the Y2038 limit.

These patches were also run through build-many-glibcs.py to ensure that
existing glibc configurations are not broken. The minimal configuration
set is x86_64-linux-gnu, aarch64-linux-gnu, powerpc-linux-gnu, and
arm-linux-gnueabi.

Albert ARIBAUD (3ADEV) (2):
  Y2038: Add 64-bit time for all architectures
  Y2038: make __tz_convert compatible with 64-bit-time

 bits/timesize.h                     | 23 ++++++++++++
 bits/timesizes.h                    | 37 ++++++++++++++++++++
 include/time.h                      | 54 +++++++++++++++++++++++------
 posix/bits/types.h                  |  8 +++++
 stdlib/Makefile                     |  2 +-
 sysdeps/x86_64/x32/bits/timesize.h  | 21 +++++++++++
 sysdeps/x86_64/x32/bits/timesizes.h | 32 +++++++++++++++++
 time/ctime.c                        | 18 ++++++++--
 time/ctime_r.c                      | 20 +++++++++--
 time/gmtime.c                       | 40 ++++++++++++++++++---
 time/localtime.c                    | 37 +++++++++++++++++---
 time/offtime.c                      | 12 +++----
 time/tzfile.c                       | 32 +++++++----------
 time/tzset.c                        | 30 +++++++---------
 14 files changed, 297 insertions(+), 69 deletions(-)
 create mode 100644 bits/timesize.h
 create mode 100644 bits/timesizes.h
 create mode 100644 sysdeps/x86_64/x32/bits/timesize.h
 create mode 100644 sysdeps/x86_64/x32/bits/timesizes.h

-- 
2.17.1

             reply	other threads:[~2018-06-16 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-16 17:13 Albert ARIBAUD (3ADEV) [this message]
2018-06-16 17:13 ` [PATCH v3 1/2] Y2038: Add 64-bit time for all architectures Albert ARIBAUD (3ADEV)
2018-06-18 11:34   ` Joseph Myers
2018-06-16 17:13 ` [PATCH v3 2/2] Y2038: make __tz_convert compatible with 64-bit-time Albert ARIBAUD (3ADEV)

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=20180616171331.25224-1-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).