From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Monday Patch Queue Review update (2023-01-09)
Date: Mon, 9 Jan 2023 10:21:04 -0500 [thread overview]
Message-ID: <cd810d71-67e0-e26f-0e41-c46ac8e47bc1@redhat.com> (raw)
Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update
Meeting: 2023-01-09 @ 0900h EST5EDT
Video/Audio: https://bbb.linuxfoundation.org/room/adm-alk-1uu-7fu
IRC: #glibc on OFTC.
Review new patches and attendee requested reviews.
With glibc 2.37 about to release the meeting reviews release blocker patches and desirable for release patches.
* State NEW delegate NOBODY is at 254 patches.
* Carlos' SLI is at 161 days up from 155 before the Holidays.
* Discussed several CI failures, some of them are "patch fails to apply"
* Raised one with DJ regarding glibc-cicd handling of binary patches from git.
* Starting at 62840
* Reviewing release blockers
* https://sourceware.org/glibc/wiki/Release/2.37
* Add _FORTIFY_SOURCE impl documentation
* Still needs review. Florian reviewed v1. v3 should be close to done.
* Fix remaining -Os/-O1 compile issues [BZ #19444]
* Adhemerval: Not exactly a release blocker but shows issues that not all optimization levels show. Some warnings show only on -O1 and not -O2.
* Carlos to look at this and the warnings.
* elf: Fix GL(dl_phdr) and GL(dl_phnum) for static builds [BZ #29864]
* Broke Alpha ABI. Needs fixing before release.
* Florian would like to review this patch.
* Remove --with-default-link option
* Florian reviewed previous version.
* Adhemerval: Added to release blockers because without this using a linker different from binutils disables vtable hardening.
* Refactor binutils configure usage
* Carlos to review given he touched the code.
* Desirable for release:
* Optimize posix_spawn signal setup with clone3
* Carlos: I would like to put in the first 4 patches.
* C2x strtol binary constant handling, C2x scanf binary constant handling (see also notes on relevant AFNOR comment)
* Important for release:
* pthread condition variable signal stealing
* Szabolcs: [v3] elf: Fix slow tls access after dlopen [BZ #19924]
* Maybe not OK for the release, but also might need more refactoring to fix the concurrency issue. This is a reasonable approach to fixing the problem.
* Cupertino: [PING,v2] Resolve-flockfile-funlockfile-differences
* The callback is passed uses the function definition, while the other one expands the macro definition.
--
Cheers,
Carlos.
reply other threads:[~2023-01-09 15:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cd810d71-67e0-e26f-0e41-c46ac8e47bc1@redhat.com \
--to=carlos@redhat.com \
--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).