From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Elmar Stellnberger <estellnb@elstel.org>,
libc-alpha@sourceware.org, libc-maintainers@gnu.org
Subject: Re: time64 functions for glibc
Date: Mon, 31 May 2021 13:01:31 -0300 [thread overview]
Message-ID: <fa203fc7-15f6-c358-3950-da1361d391e1@linaro.org> (raw)
In-Reply-To: <8bb369a7-ebc0-d108-ca38-0ba2c658df12@elstel.org>
On 31/05/2021 12:43, Elmar Stellnberger via Libc-alpha wrote:
> Dear maintainers of the glibc
>
> The year 2038 is coming soon and I still have many 32bit programs in use. There has been a draft to make glibc time64_t fit:
> https://sourceware.org/glibc/wiki/Y2038ProofnessDesign
>
> Unfortunately this has not been implemented all the years since the time has become 64bit in the kernel. Under Windows time64_t is available since long. Can you please tell me when you are planning to work on this? - I am currently programming https://www.elstel.org/atea/ and of course I would have liked to make the program time64_t fit without having to access kernel sources and without having to implement time64_t2char* conversion myself. The time implementation of libopenssl is also 32bit but it has a wraparound so that proper ASN-time usage will be possible after 2038. - And what about all the 32bit SoC computers like the Raspberry Pi? They also run Linux!!
>
> Yours Sincerely,
> Elmar Stellnberger
>
> P.S.: Please acknowledge the receival of this email before you answer.
It is on 2.34 plan [1], Carlos O'Donnel is reviewing it. Similar to LFS,
you will need a newer flag to actually enable it (-D_TIME_BITS=64).
The intended work for 2.34 still misses some ABI (utmp, utmpx, and lastlogin)
and installed programs would still use 32-bit; but it should enable
programs to proper support 64-bit.
[1] https://patchwork.sourceware.org/project/glibc/list/?series=2199
next prev parent reply other threads:[~2021-05-31 16:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 15:43 Elmar Stellnberger
2021-05-31 15:51 ` Paul Zimmermann
2021-05-31 16:01 ` Adhemerval Zanella [this message]
2021-05-31 18:46 ` Paul Eggert
2021-05-31 18:56 ` Florian Weimer
2021-05-31 19:08 ` Adhemerval Zanella
2021-05-31 19:16 ` Florian Weimer
2021-05-31 19:28 ` Adhemerval Zanella
2021-06-01 16:32 ` Elmar Stellnberger
2021-05-31 19:03 ` Adhemerval Zanella
2021-06-22 21:41 ` Paul Eggert
2021-06-23 13:29 ` Adhemerval Zanella
2021-06-23 16:59 ` Joseph Myers
2021-06-23 17:59 ` Paul Eggert
2021-06-24 17:37 ` Joseph Myers
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=fa203fc7-15f6-c358-3950-da1361d391e1@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=estellnb@elstel.org \
--cc=libc-alpha@sourceware.org \
--cc=libc-maintainers@gnu.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).