public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug string/29127] Incomplete backport causes tst-{strncmp,wcsncmp}-rtm to fail Date: Wed, 25 May 2022 22:03:09 +0000 [thread overview] Message-ID: <bug-29127-131-2RyPrX68Ln@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29127-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29127 --- Comment #2 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The release/2.35/master branch has been updated by Sunil Pandey <skpgkp2@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=ac87df8d750b0734e20ffb82d1d0d0efbe4b6212 commit ac87df8d750b0734e20ffb82d1d0d0efbe4b6212 Author: Noah Goldstein <goldstein.w.n@gmail.com> Date: Tue Feb 15 08:18:15 2022 -0600 x86: Fallback {str|wcs}cmp RTM in the ncmp overflow case [BZ #29127] Re-cherry-pick commit c627209832 for strcmp-avx2.S change which was omitted in intial cherry pick because at the time this bug was not present on release branch. Fixes BZ #29127. In the overflow fallback strncmp-avx2-rtm and wcsncmp-avx2-rtm would call strcmp-avx2 and wcscmp-avx2 respectively. This would have not checks around vzeroupper and would trigger spurious aborts. This commit fixes that. test-strcmp, test-strncmp, test-wcscmp, and test-wcsncmp all pass on AVX2 machines with and without RTM. Co-authored-by: H.J. Lu <hjl.tools@gmail.com> (cherry picked from commit c6272098323153db373f2986c67786ea8c85f1cf) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-05-25 22:03 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-07 1:17 [Bug string/29127] New: " ats-sourceware at offog dot org 2022-05-23 13:32 ` [Bug string/29127] " fweimer at redhat dot com 2022-05-23 15:25 ` goldstein.w.n at gmail dot com 2022-05-25 22:03 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-25 23:08 ` cvs-commit at gcc dot gnu.org 2022-05-25 23:11 ` cvs-commit at gcc dot gnu.org 2022-05-25 23:24 ` ats-sourceware at offog dot org 2022-05-26 3:01 ` hjl.tools at gmail dot com
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=bug-29127-131-2RyPrX68Ln@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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).