From: Carlos O'Donell <carlos@redhat.com>
To: libc-alpha <libc-alpha@sourceware.org>
Subject: Monday Patch Queue Review update (2022-01-17)
Date: Tue, 18 Jan 2022 09:00:14 -0500 [thread overview]
Message-ID: <862a3190-a5e2-d44c-09d4-77673b4793ba@redhat.com> (raw)
Most recent meeting status is always here:
https://sourceware.org/glibc/wiki/PatchworkReviewMeetings#Update
Meeting: 2022-01-17 @ 0900h EST (UTC-5)
Video/Audio: https://bluejeans.com/9093064454
IRC: #glibc on OFTC.
With the release upcoming we've switched to reviewing blockers and desirable changes.
* NEW/NOBODY 290 patches
* [v7] elf: Properly align all PT_LOAD segments [BZ #28676]
* Adhemerval to review alignment patch.
* linux: Fix ancillary 64-bit time timestamp conversion (BZ #28349, BZ #28350)
* Florian to review.
* posix: Add terminal control setting support for posix_spawn
* Carlos to finish review Monday.
* Multiple rtld-audit fixes
* Adhemerval to rebase patch set.
* Szabolcs looked at the aarch64 pieces and gave feedback.
* Properly handle --disable-default-pie
* Siddhesh is going to look at this.
* Carlos and Adhemerval discussed 64-bit time_t testing.
* No way to change library default time_t size, just testing can test it.
* Prelink discussion
* Adhemerval: May I submit patches to remove prelink?
* Carlos: Yes.
* Discussed Intel, Arm, Linaro involvement in prelink.
* Carlos: IHVs and ISVs need to invest upstream if they want to see prelink maintained.
* Paul sends his regrets and includes two items:
* I have done a review of the accuracy of the libmvec functions (in master)
both with sse4.2, avx2 and avx512. Apart from a minor issue with atan2
in binary64 which was fixed (#28765), I found no error larger than 4 ulps,
both in binary32 and binary64.
* we are making good progress in the CORE-MATH project: 17 out of 26
functions are now available in single precision (binary32).
See https://homepages.loria.fr/PZimmermann/CORE-MATH/.
In most cases the correctly-rounded CORE-MATH code outperforms the
GNU libc one (see the "perf" graphs). The only exceptions so far are
the cosf function on i7, and the expf function.
--
Cheers,
Carlos.
next reply other threads:[~2022-01-18 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 14:00 Carlos O'Donell [this message]
2022-01-24 22:10 ` Joseph Myers
2022-01-25 9:27 ` Paul Zimmermann
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=862a3190-a5e2-d44c-09d4-77673b4793ba@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).