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-04-03)
Date: Mon, 3 Apr 2023 10:01:18 -0400	[thread overview]
Message-ID: <28fe1f1f-8fad-0da0-848e-a1d90d00cb42@redhat.com> (raw)

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

Meeting: 2023-04-03 @ 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.

 * State NEW delegate NOBODY at 248 patches.
 * Carlos' SLI at 156 days.
 * https://sourceware.org/bugzilla/show_bug.cgi?id=30301 (memalign improvement introduced regressions)
  * Discussed what we need to do to fix the issue.
 * Adhemerval: Raised the issue of submitted bugs for the upcoming release?
  * Required? Desired? Useful? Filtered?
  * Carlos: Unless someone asks for a shortened NEWS list, I'd leave these there as an artifacts of showing development in progress.
  * Florian: Notes that Version field in bugzilla includes 2 upcoming versions so that bugs in devel can be tracked correctly for pre-release based on date.
 * Started at 67211
 * LoongArch: Ensure consistency with kernel by using union for struct members in mcontext_t and ucontext_t. (Caiyin Yu)
  * Noted that these changes seem odd given that any implementation can pick names as required.
 * [v2,18.2/34] hurd: Port trampoline.c to x86_64 (Sergey)
 * [v2,18.1/34] hurd: Do not declare local variables volatile (Sergey)
 * [v2] hurd: Implement sigreturn for x86_64 (Sergey)
 * x86/dl-cacheinfo: remove unsused parameter from handle_amd (Andreas)
  * Needs review from anyone. Fairly generic cleanup.
 * implement dlmem() function (stsp)
  * Carlos to comment again about dlmem().
 * build-many-glibcs.py: --disable-gcov for gcc-first (Jan-Benedict Glaw)
  * Discussed briefly to disable gcov.
  * Carlos: I'll look at this briefly to commit.
 * https://sourceware.org/bugzilla/show_bug.cgi?id=30293
  * Needs review in light of the glibc implementaiton.
 * [v2] Add tests for strdup and strndup (BZ #30266) (Joe)
  * Adhemerval reviewing test additions.
 * [v5,1/1] Created tunable to force small pages on stack allocation. (Cupertino)
  * Adhemerval to review.
  * Carlos: This seems like we should be doing this by default?
  * Florian: Guard page size could be 2MiB
  * Carlos: Split the tcb from stack?
  * Florian: Note that the reported RSS increase is not technically real because it's untouched thread stack.
  * Adding a tunable is a good first step.
 * [v3] elf: Fix slow tls access after dlopen [BZ #19924] (Szabolcs)
  * Still needs review. Important for the release.
 * [v2] manual: Document __wur usage under _FORTIFY_SOURCE (Siddhesh)
  * Florian to review.
 * Add clone3 support for multiple architectures (Adhemerval)
  * Carlos to review.
 * Stopped at 66592.

-- 
Cheers,
Carlos.


             reply	other threads:[~2023-04-03 14:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 14:01 Carlos O'Donell [this message]
2023-04-03 20:30 ` Sergey Bugaev
2023-04-04 17:48   ` Carlos O'Donell
2023-04-04 19:09     ` Sergey Bugaev
2023-04-05  6:31       ` Carlos O'Donell

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=28fe1f1f-8fad-0da0-848e-a1d90d00cb42@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).