From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>, libc-alpha@sourceware.org
Subject: Re: Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release
Date: Tue, 2 Jan 2024 11:39:05 -0300 [thread overview]
Message-ID: <68b85eb5-d7f1-4e4a-88b9-f21f99e3243b@linaro.org> (raw)
In-Reply-To: <2652861.NG923GbCHz@noumea>
On 01/01/24 10:18, Andreas K. Huettel wrote:
> Hi all,
>
> first of all, a happy new year to all of you. Let us hope for a more peaceful 2024.
>
> We follow for the upcoming glibc 2.39 the same schedule as usual.
>
> - January 1-11, "slushy ABI freeze"
> * No new ABI additions.
> * ABI corrections should be reviewed, RM approval not required.
> * Avoid any changes that require action by the ports (including all
> that require ulps regeneration)
> * Bug fixes.
> * Monday patch review switches to reviewing critical bug list and
> ABI issues.
>
> The planning section of our 2.39 wiki page lists at the moment the following items:
> https://sourceware.org/glibc/wiki/Release/2.39#Planning
>
> * Release blockers
> - Revert to original qsort implementation and apply subsequent mergesort changes with heapsort as fallback.
> Attempts to make changes to qsort have shown deep application dependencies on undocumented behaviour.
> In order to preserver application compatibility we need to revert the less conservative changes.
> It would be good to revert to the original known state and then copy in some of the final changes.
I just sent a new version [1], which should address the remarks Florian
has raised.
> - AArch64 SME support https://patchwork.sourceware.org/project/glibc/list/?series=28136
I already reviewed it and modules some minor nits it should ready to land.
> * Desirable this release?
> - Add clone3 support for multiple architectures (mips and arm missing)
It is already done.
> - Remove ia64-linux-gnu
I am just warning Linux 6.7 to be officially release. It might also require
some minor updates on the exported syscall numbers and some headers constants.
> - Implement C23 <stdbit.h>
>
> Please update what is in the meantime done / obsolete / ..., ideally with links to the commits or bugs.
Since we are aiming to implement all the remaining C23 bits, I would
like to add my floating-point round fixes as well [2]
>
> What else should we add here that still needs to go into 2.39?
The fstat alpha/sparc64 fix for sure [3]. I would like to add some gnulib
sync [4], but I can backport it if required as well.
>
> - 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.
>
> - February 1
> * glibc 2.39 release
>
> If you have any comments or objections, please reply to the list.
>
> Cheers,
> Andreas
>
[1] https://patchwork.sourceware.org/project/glibc/patch/20240102141500.3300552-1-adhemerval.zanella@linaro.org/
[2] https://patchwork.sourceware.org/project/glibc/list/?series=28918
[3] https://patchwork.sourceware.org/project/glibc/patch/20240102143152.3477636-1-adhemerval.zanella@linaro.org/
[4] https://patchwork.sourceware.org/project/glibc/patch/20231023214527.3628194-1-adhemerval.zanella@linaro.org/
next prev parent reply other threads:[~2024-01-02 14:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-01 13:18 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 ` Adhemerval Zanella Netto [this message]
2024-01-06 12:27 ` Happy New Year 2024 & Freeze for the upcoming glibc 2.39 release 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
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=68b85eb5-d7f1-4e4a-88b9-f21f99e3243b@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).