From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Jacob Avraham <jacob.avraham@auto-talks.com>,
Libc-help <libc-help@sourceware.org>
Subject: Re: support to y2038 for ARM 32b architecture
Date: Tue, 7 Dec 2021 09:48:57 -0300 [thread overview]
Message-ID: <8e18d86f-ad11-e94e-43d9-73251b4f38da@linaro.org> (raw)
In-Reply-To: <CAD_Sx11xi22b46J836fO-T67uERY2NeN1VqAG2bFZsF-h_Uuow@mail.gmail.com>
On 05/12/2021 12:39, Jacob Avraham via Libc-help wrote:
> Hi,
> Does the latest glibc version support y2038 for ARM 32bit architecture and
> if not, when is it planned for?
>
> Thanks,
> Jacob Avraham
>
Yes, since GLIBC 2.34. From NEWS file:
* Add support for 64-bit time_t on configurations like x86 where time_t
is traditionally 32-bit. Although time_t still defaults to 32-bit on
these configurations, this default may change in future versions.
This is enabled with the _TIME_BITS preprocessor macro set to 64 and is
only supported when LFS (_FILE_OFFSET_BITS=64) is also enabled. It is
only enabled for Linux and the full support requires a minimum kernel
version of 5.1.
next prev parent reply other threads:[~2021-12-07 12:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 15:39 Jacob Avraham
2021-12-07 12:48 ` Adhemerval Zanella [this message]
2021-12-07 13:42 ` Lukasz Majewski
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=8e18d86f-ad11-e94e-43d9-73251b4f38da@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=jacob.avraham@auto-talks.com \
--cc=libc-help@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).