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 (2023-01-16)
Date: Mon, 16 Jan 2023 09:42:15 -0500	[thread overview]
Message-ID: <fefc1b79-f1d1-b026-50cc-d6d4e69067d2@redhat.com> (raw)

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

Meeting: 2023-01-16 @ 0900h EST5EDT

Video/Audio: https://bbb.linuxfoundation.org/room/adm-alk-1uu-7fu

IRC: #glibc on OFTC.

Review new patches and restart review at the top.

 * Status NEW delegate NOBODY 247 patches.
 * Carlos' SLI at 160 days.
 * Two weeks until 2.37 release.
 * ABI freeze.
 * Remove --with-default-link option
  * Carlos reviewing the changes.
  * Florian to review the vtable hardening bits.
 * Status of posix_spawn with clone3?
  * New version sent with comments fixed.
  * https://patchwork.sourceware.org/project/glibc/list/?series=15920
  * Assembly impl removed. Only x86_64 and aarch64.
 * Discussed the C2X impl additions.
  * Adhemerval noted that he's reviewed the strtol changes, but it adds a lot of new symbols.
  * Carlos to post to the list and suggest scanf binary constant handling get reviews but committed only once 2.38 opens for development.
  * Adhemerval: Makes sense for next release and both should go in at the same release.
 * Discussed aarch64 optimizations from Wilco.
  * Szabolcs: Fairly safe, but could cause performance regressions on cores that we haven't benchmarked.
  * Carlos: I'm OK with those going into 2.37.
  * Carlos will reply on the first patch that it's OK going in now, but we want to avoid further changes to allow machine maintainers to test next week.
 * [v1,1/2] nptl: Changes tests to be 1/line and sorted
  * [v1,2/2] nptl: Add a testcase for inputs racey to {w}memcmp{eq} BZ #29863
   * Carlos talked to HJ to review.
   * Noah and Carlos agreed to delay to 2.37.
 * Desirable for release: AMD cache patch:
   * https://sourceware.org/pipermail/libc-alpha/2022-December/143989.html
   * Restricted to AMD cpus.
   * Reviewed-by: for Pram.
   * Should be OK to go in this week.
 * Carlos still to look at pthread condvar signal stealing for 2.37 this week.


-- 
Cheers,
Carlos.


                 reply	other threads:[~2023-01-16 14:42 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=fefc1b79-f1d1-b026-50cc-d6d4e69067d2@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).