public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: H.J. Lu <hjl@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/release/2.33/master] NEWS: Add a bug fix entry for BZ #27457 Date: Thu, 27 Jan 2022 20:21:11 +0000 (GMT) [thread overview] Message-ID: <20220127202111.D7F853858430@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=902af2f5eee71c3e48fe30d43fd7c61d563e975b commit 902af2f5eee71c3e48fe30d43fd7c61d563e975b Author: H.J. Lu <hjl.tools@gmail.com> Date: Thu Jan 27 12:20:21 2022 -0800 NEWS: Add a bug fix entry for BZ #27457 Diff: --- NEWS | 1 + 1 file changed, 1 insertion(+) diff --git a/NEWS b/NEWS index 09bb7dff66..bbec5e487a 100644 --- a/NEWS +++ b/NEWS @@ -44,6 +44,7 @@ The following bugs are resolved with this release: [23462] Static binary with dynamic string tokens ($LIB, $PLATFORM, $ORIGIN) crashes [27304] pthread_cond_destroy does not pass private flag to futex system calls + [27457] vzeroupper use in AVX2 multiarch string functions cause HTM aborts [27537] test-container: Always copy test-specific support files [27577] elf/ld.so --help doesn't work [27646] gethostbyname and NSS crashes after dlmopen
reply other threads:[~2022-01-27 20: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=20220127202111.D7F853858430@sourceware.org \ --to=hjl@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).