From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Monday Patch Queue Review update (2022-08-22)
Date: Thu, 1 Sep 2022 16:34:50 -0400 [thread overview]
Message-ID: <a71e1a81-a74f-c1e2-25a1-41d973c8eb08@redhat.com> (raw)
Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update
Meeting: 2022-08-22 @ 0900h EST5EDT
Video/Audio: https://bluejeans.com/9093064454
IRC: #glibc on OFTC.
Review new patches and attendee requested reviews.
* State NEW delegate NOBODY is at 217
* Starting at 56906
* Fix BZ #29463 in the ibm128 implementation of y1l too (mwh)
* Needs review from IBM
* [v2] Avoid undefined behaviour in ibm128 implementation of llroundl (mwh)
* Needs review from IBM
* [resend] LoongArch: Fix dl-machine.h code formatting
* Needs a quick review for code formatting.
* LoongArch: Use __builtin_{fmax,fmaxf,fmin,fminf} with GCC >= 13
* Needs review.
* codonell: Who is the LoongArch machine maintainer?
* Such a machine maintainer could push machine patches.
* Caiyin Yu? Should discuss this with Caiyin.
* adhemerval: Who is syncing the translations?
* codonell: I am to release/2.36/master.
* Check ld.so/libc.so consistency during startup (fweimer)
* codonell: I want to review this today.
* vfprintf refactor (fweimer)
* Needs review.
* Review required for buffer implementation.
* [1/1] LoongArch: Fix ptr mangling/demangling features. (caiyinyu)
* Needs changes.
* Add AArch64 HWCAP2_* constants from Linux 5.19 (joseh)
* szabolcs will review.
* Add NT_LOONGARCH_* from Linux 5.19 to elf.h
* Will ask Caiyin Yu to review?
* Needs LoongArch maintainer to review.
* Stopped at 56821.
* Forced ordering for DFS ELF dependency sorting (bug 28937) (fweimer)
* codonell: Would be great to fix this for the new sort algo.
* adhemerval: I'll review.
* An update with regards to the DT_HASH situation?
* adhemerval: We should keep DT_HASH. This is an issue of optics.
* fweimer: This is a difficult decision that we should wait to determine
if we know all of the details of what works and doesn't work.
* codonell: I can make a public statement around this.
* [v4] elf: Remove -fno-tree-loop-distribute-patterns usage on dl-support (adhemerval)
* Needs review.
* [v3] debug: test for more required cacellation points (BZ# 29274)
* Still needs review from Carlos.
--
Cheers,
Carlos.
reply other threads:[~2022-09-01 20:34 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=a71e1a81-a74f-c1e2-25a1-41d973c8eb08@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).