From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Monday Patch Queue Review update (2022-05-30)
Date: Mon, 30 May 2022 17:21:28 -0400 [thread overview]
Message-ID: <1d18d8d6-4bbd-d177-8aac-df1e73811f01@redhat.com> (raw)
Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update
Meeting: 2022-05-30 @ 0900h EST5EDT
Video/Audio: https://bluejeans.com/9093064454
IRC: #glibc on OFTC.
Review new patches and attendee requested reviews.
* State NEW delegate NOBODY, 228 patches.
* Starting at 54476
* elf: Remove ELF_RTYPE_CLASS_EXTERN_PROTECTED_DATA (Fangrui Song)
* Needs review. Szabolcs: Same as aarch64.
* This never worked.
* [v2] elf: Remove one-default-version check when searching an unversioned symbol (Fangrui Song)
* Florian made a comment about the underlying semantics.
* [v1] benchtests: Improve benchtests for strstr, memmem, and memchr (Noah)
* Already pushed.
* posix: Fix getconf symbolic constants defined in limits.h (BZ# 29147) (Adhemerval)
* Review if the minimum impacts applications.
* elf: Fix handling of symbol versions which hash to zero (bug 29190) (Florian Weimer)
* Found all uppercase P's that hash to zero.
* [1/1] x86_64: Add strstr function with 512-bit EVEX (Raghuveer Devulapalli)
* Noah updated the benchmark for this.
* Adhemerval: Can we make this more generic?
* Noah: Wilco's version is simply better.
* Remove _dl_skip_args (Adhemerval)
* Needs review.
* Some machime maintainers have reviewed.
* i686,x86_64: Done, hppa: Reviewed, aarch64: Already done.
* Stopped at 54394.
* Discussed "linux: Add fallback for clone failure on posix_spawn (BZ #29115)"
* The issues goes far beyond glibc.
* If we make posix_spawn work then users can use this.
* Adhemerval: Rewriting with shared mapping.
* Florian: Always use a shared mapping the first time to detect vfork-as-fork.
* Just a future direction for the code.
* Reminder: GNU Tools Cauldron 2022
* https://gcc.gnu.org/wiki/cauldron2022
* We can review the patch queue in person!
--
Cheers,
Carlos.
next reply other threads:[~2022-05-30 21:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 21:21 Carlos O'Donell [this message]
2022-05-30 23:18 ` Noah Goldstein
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=1d18d8d6-4bbd-d177-8aac-df1e73811f01@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).