Re: Year 2038 issue

From: Date: Mon, 16 Jun 2025 17:23:45 +0000
Subject: Re: Year 2038 issue
References: 1 2 3  Groups: php.internals 
Request: Send a blank email to internals+get-127688@lists.php.net to get a copy of this message
On 16.06.25 17:21, Rob Landers wrote:
On Mon, Jun 16, 2025, at 16:54, Alexandru Pătrănescu wrote:
On Mon, Jun 16, 2025 at 4:03 PM Marc Bennewitz <marc@mabe.berlin> wrote:
    Hi all,
    It's 12.5 years only until the timestamps in PHP on 32bit will
    not work
    as expected anymore.
Hi, I think that maybe we can already deprecate supporting 32 bit builds. And, maybe with PHP 9, or PHP 10, or with a future version that might exist in about 6/7 years, completely drop 32 bits support. As far as I checked a bit, all major OSs where PHP could run already dropped or will drop support for 32 bits builds. I expect that at some point even the linux kernel will drop support. The impacted runtimes will probably be very low. -- Alex
100% agree. We are already running out of space on some bitmasks (there are a couple with exactly one bit left, or even none in the case of GC flags) for 32 bit support.
Dropping 32bit builds entirely is an option I would support as well. Would you be able to help me writing an RFC for it as I don't have enough knowledge of PHP internals to know where 32bit build is going to be problematic there as well?
— Rob


Attachment: [application/pgp-keys] OpenPGP public key OpenPGP_0x3936ABF753BC88CE.asc
Attachment: [application/pgp-signature] OpenPGP digital signature OpenPGP_signature.asc
« previous php.internals (#127688) next »