From: Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha <libc-alpha@sourceware.org>,
DJ Delorie <dj@redhat.com>, caiyinyu <caiyinyu@loongson.cn>,
Vineet Gupta <vineetg@rivosinc.com>
Subject: Monday Patch Queue Review update (2022-11-28)
Date: Mon, 28 Nov 2022 09:53:15 -0500 [thread overview]
Message-ID: <7c609c77-25f7-9708-da2d-ce80633c0a32@redhat.com> (raw)
Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update
Meeting: 2022-11-28 @ 0900h EST5EDT
Video/Audio: https://bluejeans.com/9093064454
IRC: #glibc on OFTC.
Review new patches and restart review at the top.
* State NEW delegate NOBODY at 253.
* Carlos' SLI at 136 days.
* Starting at 61164
* <time.h>: Make strptime available by default (fweimer)
* C99 changes.
* <signal.h>: Make bsd_signal available with _GNU_SOURCE (fweimer)
* C99 changes.
* [v3,1/2] scripts: Add "|" operator support to glibcpp's parsing (shahab)
* Reviewd by Florian.
* [v3,2/2] ARC: update definitions in elf/elf.h (shahab)
* Needs review by Vineet Gupta (machine maintainer)
* Add restrict annotations to all functions that require it (Seija)
* Adhemerval to comment that this changes internal functions and should split.
* CI - Patch fails to apply?
* Discussed RFC on malloc usable size and systemd usage of remainder of bytes.
* libio: Deprecate the fcloseall function (bug 28099) (fweimer)
* fcloseall is problematic from an API perspective.
* Deprecate this release then find a release to switch to backwards compat.
* [v2] <stdio.h>: Make fopencookie, vasprintf, asprintf available by default (fweimer)
* C99 changes.
* <string.h>: Make strchrnul, strcasestr, memmem available by default
* C99 changes.
* [v2] Resolve-flockfile-funlockfile-differences (patrick)
* Under review by Florian.
* LoongArch: Use medium cmodel build libc_nonshared.a. (caiyinyu)
* Changes requested.
* Series: LoongArch: Use builtins with GCC >= 13 (xiaolin)
* LoongArch maintainers need to review.
* Revert "Correctly determine libc.so 'OUTPUT_FORMAT' when cross-compiling." (Vineet)
* Carlos to review.
* [v2] dlsym: Add RTLD_PROBE to dlsym only probe symbol without add dependency. (wang)
* Discussed that Solaris has RTLD_PROBE, but semantics are different.
* Need to discuss on list that this may not be needed given the existing requirements.
* LoongArch: Add syscall.c for getting correct return value (XingLi)
* Changes requested.
* malloc: Use correct C11 atomics for fastbin (wilco)
* Needs performance review? Could DJ have a look at this?
* Last time we tried to do this it had a performance regression.
* Needs review.
* Stopped at 60930
* Siddhesh looking for feedback on RFC for malloc_usable_size
* https://sourceware.org/pipermail/libc-alpha/2022-November/143599.html
* Adhemerval: Status of "Remove Linux generic sysdep" review?
* Carlos: Tested it before I went on vacation. Looks good. Want to retest.
* Adhemerval: v2 of "Optimize posix_spawn signal setup with clone3"
* Carlos: Early commit for this would be nice so machine maintainers.
* Adhemerval: Status of "Fixing remaining lld issues"
* 3 patches with fweimer for review.
--
Cheers,
Carlos.
reply other threads:[~2022-11-28 14:53 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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7c609c77-25f7-9708-da2d-ce80633c0a32@redhat.com \
--to=libc-alpha@sourceware.org \
--cc=caiyinyu@loongson.cn \
--cc=carlos@redhat.com \
--cc=dj@redhat.com \
--cc=vineetg@rivosinc.com \
/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).