From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Monday Patch Queue Review update (2022-08-15)
Date: Mon, 15 Aug 2022 10:17:31 -0400 [thread overview]
Message-ID: <c7483968-3656-64a6-9548-5978531d8f07@redhat.com> (raw)
Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update
Meeting: 2022-08-15 @ 0900h EST5EDT
Video/Audio: https://bluejeans.com/9093064454
IRC: #glibc on OFTC.
Review new patches and attendee requested reviews.
* State NEW delegate NOBODY at 225 patches.
* LoongArch: Add optimized functions.
* Noah: Anything with optimized would be nice to have microbenchmark numbers.
* Carlos: I'll review and ask for the microbenchmark numbers.
* Linux: Terminate subprocess on late failure in tst-pidfd (bug 29485)
* Florian: Need to terminate the process.
* netinet/in.h: Add ip_mreqn structure (Samuel Thibaut)
* Florian: I'll write a follow up.
* Ensure calculations happen with desired rounding mode in y1lf128 (Michael)
* Needs review from IBM.
* Improve performance of libc locks (Wilco)
* Carlos: I'll review and ask for the microbenchmark numbers.
* Siddhesh: This is a generic change that needs to show numbers.
* [v4] elf: Remove -fno-tree-loop-distribute-patterns usage on dl-support (Adhemerval)
* Needs review.
* nss_dns: Fix handling of non-host CNAMEs (bug 12154) (Florian)
* Siddhesh will look at the series.
* sunrpc: Stub out getpublickey, getsecretkey, authdes_create (Florian)
* Carlos: We got rid of configure, and TIRPC can only be used.
Even if you could use a non-files 'key' provider we don't
want to support this.
* malloc: Do not use MAP_NORESERVE to allocate heap segments (Florian)
* Reviewed by Siddhesh.
* Stopped at 56583.
* Noah asked about the status of strlcpy and strlcat.
* These are still with the Austin Group for deliberation and addition to POSIX.
* Likely to be discussed at the next telecon.
* There is a defect report against these interfaces filed by Paul Eggert.
* We are waiting for the Austin Group to deliberate.
* Noah has optimized versions of these routines that could go into glibc.
--
Cheers,
Carlos.
reply other threads:[~2022-08-15 14:17 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=c7483968-3656-64a6-9548-5978531d8f07@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).