Re: freeze for the upcoming glibc 2.38 release

[Xi Ruoyao <xry111@xry111.site>]

On Thu, 2023-07-06 at 20:28 +0200, Andreas K. Huettel via Libc-alpha
wrote:

> - July 6-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.
> 
>   We still have two "desirables" on the wiki page, 
>   * "Add clone3 support for multiple architectures" - can we wrap this
> up
>     safely next week?
>     https://patchwork.sourceware.org/project/glibc/list/?series=16730
>   * "Flip defaults for some security-relevant build configuration
> flags"
>     https://patchwork.sourceware.org/project/glibc/list/?series=21908
>     The series consists of 4 patches. 2 (stack-protector-strong), 3 
>     (bind-now) and 4 (disable-crypt) should be uncontroversial.
>     ## The list thread on 1 (autoconf-2.71) ended without a clear
>        conclusion. What's the status here? ##
> 
>   Anything else?

May I add
https://patchwork.sourceware.org/project/glibc/list/?series=22006 here?
The reason:

- It's trivial.
- Applying it here will stop GCC analyzer developers from implementing
these as special cases.

-- 
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University