From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>, libc-alpha@sourceware.org
Subject: Re: Freeze for the upcoming glibc 2.39 release - status
Date: Fri, 12 Jan 2024 07:56:10 -0300 [thread overview]
Message-ID: <f981b9ea-fb44-4bab-a858-0806e36d76b7@linaro.org> (raw)
In-Reply-To: <2030348.PIDvDuAF1L@pinacolada>
On 11/01/24 19:24, Andreas K. Huettel wrote:
>>
>> We follow for the upcoming glibc 2.39 the same schedule as usual.
>>
>> - January 12-31, "hard ABI freeze"
>> * Noncritical bug fixes.
>> * No ABI changes without RM discussion.
>> * High risk bug fixes should be discussed on the list.
>
> Going through the mailing list I've come across the following unresolved threads.
> Please have a look. Comments welcome.
>
> I'm on vacation travelling next week (Sun-Sat), which means limited e-mail access.
>
>
> [PATCH v2] stdlib: Reinstate stable mergesort implementation on qsort
> https://patchwork.sourceware.org/project/glibc/list/?series=29039
> delegated, Florian is looking at this
> release blocker
>
> [PATCH v2] linux: Fix fstat64 on alpha and sparc64
> https://patchwork.sourceware.org/project/glibc/list/?series=29040
> needs review
> release blocker
>
This might the cause of the buildbot issues, since it makes the loader
fail.
>
> [PATCH v2] Make __getrandom_nocancel set errno and add a _nostatus version
> https://patchwork.sourceware.org/project/glibc/list/?series=29130
> R-B Adhemerval
> bug fix - should go in now?
>
Yes, I think it would be good.
> [PATCH] debug/getwd_chk.c: warning should be emitted for the __getwd_chk symbol
> https://patchwork.sourceware.org/project/glibc/list/?series=27941
> R-B Adhemerval
> bug fix - should go in now
>
Yes, this seems a straightforward fix.
>
> [PATCH v3] RISC-V: Enable static-pie
> https://patchwork.sourceware.org/project/glibc/list/?series=29034
> R-B Adhemerval
> feature - could be in already - now or after release?
The change is small and it can be disable by a configure switch, so
I think it would be ok to install.
>
> [PATCH] math: remove exp10 wrappers
> https://patchwork.sourceware.org/project/glibc/list/?series=29463
> R-B Adhemerval
> feature - could go in now, last minute for it
Yes, I think so.
>
>
> [PATCH v11 0/7] RISC-V: ifunced memcpy using new kernel hwprobe interface
> https://patchwork.sourceware.org/project/glibc/list/?series=29471
> needs another review?
> lots of code, but already many iterations - soon or after release
>
> [PATCH] x86-64: Check if mprotect works before rewriting PLT
> https://patchwork.sourceware.org/project/glibc/list/?series=29560
> needs review / discussion?
>
> [PATCH v3] rtld: Add glibc.rtld.enable_secure tunable
> https://patchwork.sourceware.org/project/glibc/list/?series=29055
> needs review, test failure
> feature - after release
>
>
>
>>
>> - February 1
>> * glibc 2.39 release
>>
>> If you have any comments or objections, please reply to the list.
>>
>> Cheers,
>> Andreas
>>
>>
>
>
next prev parent reply other threads:[~2024-01-12 10:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 13:18 Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release Andreas K. Huettel
2024-01-02 9:14 ` Florian Weimer
2024-01-02 9:21 ` autoconf 2.72 ? (Re: Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release) Andreas K. Huettel
2024-01-02 10:27 ` Florian Weimer
2024-01-02 17:35 ` Paul Eggert
2024-01-02 19:17 ` [PATCH, test conversion, RFC] Convert to autoconf 2.72 (no patches) Andreas K. Hüttel
2024-01-02 21:30 ` Florian Weimer
2024-01-03 4:13 ` Paul Eggert
2024-01-10 18:37 ` Carlos O'Donell
2024-01-02 14:39 ` Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release Adhemerval Zanella Netto
2024-01-06 12:27 ` Andreas K. Huettel
2024-01-08 12:54 ` Adhemerval Zanella Netto
2024-01-02 15:22 ` H.J. Lu
2024-01-06 22:29 ` Andreas K. Huettel
2024-01-03 21:57 ` enh
2024-01-10 18:38 ` Carlos O'Donell
2024-01-10 20:33 ` Jeff Law
2024-01-11 1:10 ` Palmer Dabbelt
2024-01-12 6:13 ` Palmer Dabbelt
2024-01-11 22:24 ` Freeze for the upcoming glibc 2.39 release - status Andreas K. Huettel
2024-01-12 10:56 ` Adhemerval Zanella Netto [this message]
2024-01-12 13:14 ` Xi Ruoyao
2024-01-12 13:25 ` Andreas K. Huettel
2024-01-12 14:23 ` Andreas K. Huettel
2024-01-12 17:19 ` Carlos O'Donell
2024-01-12 17:34 ` Palmer Dabbelt
2024-01-12 18:10 ` Adhemerval Zanella Netto
2024-01-12 22:10 ` Palmer Dabbelt
2024-01-12 22:21 ` Freeze for the upcoming glibc 2.39 release - status (2) Andreas K. Huettel
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=f981b9ea-fb44-4bab-a858-0806e36d76b7@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=dilfridge@gentoo.org \
--cc=libc-alpha@sourceware.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).