[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] year2038: support glibc 2.34 _TIME_BITS=64

From: Florian Weimer
Subject: Re: [PATCH] year2038: support glibc 2.34 _TIME_BITS=64
Date: Thu, 08 Jul 2021 07:36:11 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)

* Paul Eggert:

> On 7/7/21 1:45 AM, Florian Weimer wrote:
>> Y2038 support requires recompilation.  If you are able to do that, why
>> not recompile for a 64-bit architecture?
> Doesn't this argue against _TIME_BITS=64 in general? It seems to be
> saying that one should just recompile for 64-bit, and never use 
> _TIME_BITS=64.

I think it does, but apparently 32-bit Arm is an outlier, related to
DRAM sizes.  I'm still not convinced that glibc needs to support that,
but the community wasn't opposed to it.

>> This probably needs per-package/component work to enable dual ABI,
>> similar to what glibc did for its time_t interfaces....
>> I don't expect many upstreams to support this effort.
> Agreed.
>> Two separate i386 ports seem to require the least human
>> resources to maintain.
> That's a reasonable approach and if people want to do that they can,
> even with the latest Gnulib and the next version of Glibc.
> However, people who want to run old binaries will surely stick to the
> 32-bit-time_t i386 port, which means they won't use the 64-bit-time_t 
> i386 port. So it's not clear to me that they will cotton to this approach.

Sorry, I don't understand.  Which approach?

I expect the legacy i386 port to be the main one.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]