glibc 2.32 release: Status of 64-bit time_t ?

[Lukasz Majewski]

Hi Carlos,

> What is the status of 64-bit time_t for glibc 2.32?
> 
> If the 32-bit RISC-V port depends on 64-bit time_t then we'll need
> to get everything sorted before we can put in the 32-bit RISC-V
> patches?
> 
> Likewise for the ARC port.
> 
> What is left for 64-bit time_t, just the semctl patches that
> Adhemerval is reviewing?
> 
> What else?

Please find up to date summary of Y2038 work for ARM:
https://github.com/lmajewski/y2038_glibc/commit/d761ad2558deafe80d8dbeb2e39961892e759155

Currently, I'm developing conversion patch for futex_time64 usage. This
seems to be a bit challenging, as for nptl and pthreads a lot of
combined C preprocessor macros are used...

> 
> I know Florian recently found a regression here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1831239
> 
> Please put these blockers or desirable patches into the release page:
> https://sourceware.org/glibc/wiki/Release/2.32#Planning
> 
> Putting them on the page helps us track resolution and status.
> 




Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://sourceware.org/pipermail/libc-alpha/attachments/20200701/3a8797a1/attachment.sig>