public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Monday Patch Queue Review update (2021-10-25)
Date: Fri, 29 Oct 2021 15:21:05 -0400	[thread overview]
Message-ID: <6d437c71-74f5-5177-adb1-9a151804bd53@redhat.com> (raw)

Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update

Meeting: 2021-10-25 @ 0900h EST (UTC-5)

Video/Audio: https://bluejeans.com/9093064454

IRC: #glibc on OFTC.

Review new patches and restart review at the top.

 * State NEW, Delegate NOBODY, 304 patches.
 * Series 4140, Improve hypot(), Adhemerval to rebase.
  * Needs rebase after HJs benchtests/Makefile change.
 * Series 4116, [v14,1/4] String: Add support for __memcmpeq() ABI on all targets
  * Looks OK.
 * Series 4105, powerpc: Use the correct flag for 32-bit known libraries
  * This looks like old a.out code is blocking this.
  * Carlos & Florian to bring up with IBM.
 * Series 4101, Add missing math functions to benchtests (Sunil Pandey)
  * Adding functions to libmvec
  * Adding benchmark data for existing libmvec functions.
  * For each function we have both double and float.
  * In order to generate the microbenchmarks for float we need float and double.
  * Sunil copied the input from double to float.
 * Series 4056, manual: remove an obsolete requirement on aligned_alloc() usage
  * Carlos to ask Martin Sebor.
  * Update 2021-10-25: Asked Martin for comment.
  * https://patchwork.sourceware.org/project/glibc/patch/33ec9e0c1e587813b90e8aa771c2c8e6e379dd48.camel@posteo.net/
 * Series 3961, [PING,8] localedata: add new locale ab_GE
  * First issues: No feedback from Rafal and Mike (other locale maintainers).
  * Second issue: Consensus on header.
   * Carlos to respond on the second issue with new thread.
   * https://sourceware.org/pipermail/libc-alpha/2021-September/130692.html
 * Series 3949, regex: fix buffer read overrun in search [BZ#28470]
  * Stuck on review. Needs v2. Marked Changes Requested given Andreas' comments.
 * Series 3941, Benchtests: Improve bench-memcpy-random
  * Siddhesh to look at improvement and reveiw.
 * Series 3895, [v2] elf: Support DT_RELR relative relocation format [BZ #27924]
  * Unknown dynamic tags are ignored by old glibc.
   * Old glibc must fail when running the new binary.
   * Need to add symbol dependency or bump ELF OSABI.
  * lld is there for review, but additional patches are needed to build glibc for tests.
   * More work is required in the tree to get lld working.
   * If the testsuite fails to build we can't talk about regressions easily.
   * What is the status of lld building with glibc?
    * Carlos: Ask on thread about status of lld to build glibc.
 * HJ: Testing gcc with glibc 2.34 issues.
  * Sanitizer libraries has a hack that they assume dlsym malloc is always freed.
   * In glibc 2.34 in dlsym we do 2 mallocs and then do 2 frees. Hack doesn't work.
  * https://bugs.llvm.org/show_bug.cgi?id=52278
 * Adhemerval: 64-bit time_t receive message fix.
  * https://patchwork.sourceware.org/project/glibc/list/?series=3280


-- 
Cheers,
Carlos.


                 reply	other threads:[~2021-10-29 19: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=6d437c71-74f5-5177-adb1-9a151804bd53@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).