public inbox for libc-stable@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Florian Weimer via Libc-stable <libc-stable@sourceware.org>
Subject: Re: [PATCH 2.39] Always define __USE_TIME_BITS64 when 64 bit time_t is used
Date: Thu, 09 May 2024 19:47:28 +0200	[thread overview]
Message-ID: <87zfsynahb.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <87fruzgu35.fsf@oldenburg.str.redhat.com> (Florian Weimer via Libc-stable's message of "Fri, 03 May 2024 10:47:42 +0200")

* Florian Weimer via Libc-stable:

> From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
>
> It was raised on libc-help [1] that some Linux kernel interfaces expect
> the libc to define __USE_TIME_BITS64 to indicate the time_t size for the
> kABI.  Different than defined by the initial y2038 design document [2],
> the __USE_TIME_BITS64 is only defined for ABIs that support more than
> one time_t size (by defining the _TIME_BITS for each module).
>
> The 64 bit time_t redirects are now enabled using a different internal
> define (__USE_TIME64_REDIRECTS). There is no expected change in semantic
> or code generation.
>
> Checked on x86_64-linux-gnu, i686-linux-gnu, aarch64-linux-gnu, and
> arm-linux-gnueabi
>
> [1] https://sourceware.org/pipermail/libc-help/2024-January/006557.html
> [2] https://sourceware.org/glibc/wiki/Y2038ProofnessDesign
>
> Reviewed-by: DJ Delorie <dj@redhat.com>
> (cherry picked from commit a4ed0471d71739928a0d0fa3258b3ff3b158e9b9)

Adhemerval, any thoughts about the backport to 2.39?

Thanks,
Florian


  parent reply	other threads:[~2024-05-09 17:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03  8:47 Florian Weimer
2024-05-03  8:48 ` [PATCH 2.39] Reinstate generic features-time64.h Florian Weimer
2024-05-09 17:47 ` Florian Weimer [this message]
2024-05-27 15:24 ` [PATCH 2.39] Always define __USE_TIME_BITS64 when 64 bit time_t is used Florian Weimer
2024-05-27 21:52   ` Adhemerval Zanella
2024-06-06 18:49 Reilly Brogan
2024-06-06 20:12 ` Adhemerval Zanella Netto
2024-06-07  8:58   ` Sam James

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=87zfsynahb.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-stable@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).