glibc 2.32 release: Status of 64-bit time_t ?

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

glibc 2.32 release: Status of 64-bit time_t ?

Sourceware - libc-alpha mailing list
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?

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.

--
Cheers,
Carlos.

Reply | Threaded
Open this post in threaded view
|

Re: glibc 2.32 release: Status of 64-bit time_t ?

Sourceware - libc-alpha mailing list


On 30/06/2020 13:53, Carlos O'Donell wrote:
> 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?

I am in fact wrapping up the work for the remaining sysvipc, just checking
on the affected architecture if something regress.  I plan to send patch
today still.

>
> What else?
>
> 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.
>
Reply | Threaded
Open this post in threaded view
|

Re: glibc 2.32 release: Status of 64-bit time_t ?

Sourceware - libc-alpha mailing list
On 6/30/20 1:10 PM, Adhemerval Zanella wrote:

>
>
> On 30/06/2020 13:53, Carlos O'Donell wrote:
>> 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?
>
> I am in fact wrapping up the work for the remaining sysvipc, just checking
> on the affected architecture if something regress.  I plan to send patch
> today still.

Please add it to the release blockers.

>>
>> What else?
>>
>> 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.
>>
>


--
Cheers,
Carlos.

Reply | Threaded
Open this post in threaded view
|

Re: glibc 2.32 release: Status of 64-bit time_t ?

Lukasz Majewski
In reply to this post by Sourceware - libc-alpha mailing list
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: [hidden email]

attachment0 (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: glibc 2.32 release: Status of 64-bit time_t ?

Sourceware - libc-alpha mailing list
In reply to this post by Sourceware - libc-alpha mailing list
"Carlos O'Donell" <[hidden email]> writes:
> 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?

It does:

"This is based on the original work from Zong Li [1] and has been
 updated to use a 64-bit time_t."

https://sourceware.org/pipermail/libc-alpha/2020-June/114675.html

Reply | Threaded
Open this post in threaded view
|

Re: glibc 2.32 release: Status of 64-bit time_t ?

Sourceware - libc-alpha mailing list
On Tue, Jun 30, 2020 at 6:47 PM DJ Delorie via Libc-alpha
<[hidden email]> wrote:

>
> "Carlos O'Donell" <[hidden email]> writes:
> > 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?
>
> It does:
>
> "This is based on the original work from Zong Li [1] and has been
>  updated to use a 64-bit time_t."
>
> https://sourceware.org/pipermail/libc-alpha/2020-June/114675.html

Sorry, I missed this email.

The RV32 port depends on 64-bit time_t. As RV32 only supports 64-bit
time_t (compared to the ARM port which has to support both 32-bit and
64-bit) we have significantly less work required.

Once Adhemerval's semctl patch series goes in everything should be
ready for RV32 support.

Alistair

>