Upcoming glibc-2.42 release
Yury Khrustalev
yury.khrustalev@arm.com
Mon Jun 16 14:09:04 GMT 2025
Hi,
On Thu, Jun 12, 2025 at 04:04:54PM +0200, Andreas K. Huettel wrote:
> Hi all,
>
> unless someone else wants to step in, I'm going to take care of the upcoming
> release again.
>
> Suggested 6-week schedule, mostly just writing down how we've handled things
> in the past:
>
> - 20 June 2024: Soft freeze
> * No *starting* of new features anymore
> * Decisions on what goes still in and what goes not
> * Review and addition of patches
>
> - 4 July 2025: Freeze
> * Machine testing
> * Bug fixes without large impact
> * No ABI changes without RM discussion
> * High risk bug fixes should be discussed on the list.
>
> - 18 July 2025: Hard freeze
> * Only critically important or technically straightforward bug fixes
>
> - 1 Aug 2025 (or ideally a bit earlier): Release
>
> Cheers,
> Andreas
>
> --
> Andreas K. H�ttel
> dilfridge@gentoo.org
> Gentoo Linux developer
> (council, toolchain, base-system, perl, libreoffice)
I'm OK with the proposed schedule however I'd like the following change, that
is currently under review and discussion, to be included in the upcoming release:
1) clear ZA state of SME before clone and clone3
https://inbox.sourceware.org/libc-alpha/20250609121407.3316070-1-yury.khrustalev@arm.com/
And two smaller changes:
2) simplify calls to __libc_arm_za_disable in assembly
https://inbox.sourceware.org/libc-alpha/20250616122527.543248-1-yury.khrustalev@arm.com/
3) GCS: use internal struct in __alloc_gcs
https://inbox.sourceware.org/libc-alpha/20250616122317.530220-1-yury.khrustalev@arm.com/
Thanks,
Yury
More information about the Libc-alpha
mailing list