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-12-13)
Date: Mon, 13 Dec 2021 10:03:01 -0500	[thread overview]
Message-ID: <20df2770-4611-e9b1-a59a-95cf2d34189b@redhat.com> (raw)

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

Meeting: 2021-12-13 @ 0900h EST (UTC-5)

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

IRC: #glibc on OFTC.

Review new patches and restart review at the top.

 * Carlos asks what are we looking at putting into the release.
 * Adhemerval:
  * Would like to get hugepage support into 2.35.
   * Siddhesh: Reviewed the last patch set.
   * Huge page support aligns with what we are doing with the text segment
    * Makes it easier to support THP with .text.
  * Carlos: What is the status of the LD_AUDIT series?
   * Adhemerval: Florian has reviewed half of the patches.
   * Florian: Ran out of time last week. I should be able to review this week.
 * Florian:
  * _dl_find_object needs review.
   * Adhemerval: Will review.
  * Minor fix to rseq. No ABI implications.
   * Removes not-needed relocations.
  * Add membarrier support (syscall wrapper)
   * Need to do some digging for programming model.
   * May be an additional step required for membarrier setup.
 * HJ:
  * libmvec patches are very large (42 patches)
   * Submit one function. Work with community to address concerns.
     If the community agrees with the approach then the rest of the
     patches can be automated and ready.
   * Intent is to include the functions in 2.35.
  * DT_RUNPATH v3 posted.
   * Carlos to review v3.
 * Sunil:
  * libmvec needs review.
   * CFI escape? Compiler generated. Encodes the DFA expression.
    * Can we remove it? What are they?
 * Siddhesh:
  * No additional reviews required.
 * Szabolcs:
  * No additional patches for review.
 * Carlos:
  * pthread cond var fix and review. Bug fix.
  * Licked the cookie. MUST BE FIXED.
 * Series 5728: Fix 64-bit time_t ancillary socket conversion
  * Posted v3. Needs review from Florian.
 * Series 5725: [v4] elf: Add _dl_find_object function
  * Adhemerval to review.
 * Series 5714: fix p_align on PT_LOAD segment in DSO isn't honored
  * Checked in.
 * Series 2348: [v2] Use LFS and 64 bit time for installed programs (BZ #15333)
  * Needed.
 * Discussed alignment issues with some architectures from the PT_LOAD changes.
  * Still need this if p_align is large.
  * We can solve this in the loader.
  * Once we fix hte linker the normal binary will have 4KiB p_align.
  * Will only get the large alignment if we have a variable that needs it.
  * For huge page we still want the large p_align even if there is no variables.
  * TODO: Must fix unmapping for 2.35.
 * Series 5703: intl/plural.y: define macros to avoid multiple conflicting declarations of yyerror and yylex
  * Ask Arjun to review this change.
 * Series 5688: [v3] Support target specific ALIGN for variable alignment test [BZ #28676]
  * Needs review.
 * Series 5695: [v7] elf: Don't execute shared object directly [BZ #28453]
  * Needs review.
 * What is the state of the OpenRISC or1k port?
  * Joseph has reviewed some of the state.
  * Is this ready for glibc 2.35?
  * State of the port is looking good.
  * Need to check build-many-glibcs and with Jospeh for the state of the port.
  * Doesn't look like there are any large blockers for 2.35.
 * New ld sort algorithm is failing on OpenRISC.
  * Needs review.
 * New ld sort default should be flipped to new algorithm.
  * Need to flip the new sort.

-- 
Cheers,
Carlos.


             reply	other threads:[~2021-12-13 15:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 15:03 Carlos O'Donell [this message]
2021-12-13 15:29 ` Florian Weimer

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=20df2770-4611-e9b1-a59a-95cf2d34189b@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).