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/29611] Optimized AVX2 string functions unconditionally use BMI2 instructions Date: Mon, 03 Oct 2022 22:02:12 +0000 [thread overview] Message-ID: <bug-29611-131-8mRsm7kB3r@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29611-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29611 --- Comment #53 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The release/2.34/master branch has been updated by Aurelien Jarno <aurel32@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=414fc856ff4e011e62b88a21d30294637a152dc7 commit 414fc856ff4e011e62b88a21d30294637a152dc7 Author: Aurelien Jarno <aurelien@aurel32.net> Date: Mon Oct 3 23:16:46 2022 +0200 x86-64: Require BMI2 for AVX2 str(n)casecmp implementations The AVX2 str(n)casecmp implementations use the 'bzhi' instruction, which belongs to the BMI2 CPU feature. NB: It also uses the 'tzcnt' BMI1 instruction, but it is executed as BSF as BSF if the CPU doesn't support TZCNT, and produces the same result for non-zero input. Partially fixes: b77b06e0e296 ("x86: Optimize strcmp-avx2.S") Partially resolves: BZ #29611 Reviewed-by: Noah Goldstein <goldstein.w.n@gmail.com> (cherry picked from commit 10f79d3670b036925da63dc532b122d27ce65ff8) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-10-03 22:02 UTC|newest] Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-25 8:17 [Bug string/29611] New: " aurelien at aurel32 dot net 2022-09-25 11:40 ` [Bug string/29611] " aurelien at aurel32 dot net 2022-09-25 13:57 ` goldstein.w.n at gmail dot com 2022-09-25 14:09 ` goldstein.w.n at gmail dot com 2022-09-25 14:11 ` goldstein.w.n at gmail dot com 2022-09-26 5:18 ` aurelien at aurel32 dot net 2022-09-26 5:19 ` aurelien at aurel32 dot net 2022-09-26 14:05 ` goldstein.w.n at gmail dot com 2022-09-26 17:52 ` hjl.tools at gmail dot com 2022-09-28 14:01 ` skpgkp2 at gmail dot com 2022-09-28 14:01 ` skpgkp2 at gmail dot com 2022-09-28 15:01 ` goldstein.w.n at gmail dot com 2022-09-28 15:10 ` aurelien at aurel32 dot net 2022-09-28 15:52 ` goldstein.w.n at gmail dot com 2022-09-28 15:57 ` skpgkp2 at gmail dot com 2022-09-28 23:14 ` skpgkp2 at gmail dot com 2022-09-28 23:15 ` skpgkp2 at gmail dot com 2022-09-29 1:26 ` hjl.tools at gmail dot com 2022-09-29 1:59 ` cvs-commit at gcc dot gnu.org 2022-09-29 1:59 ` cvs-commit at gcc dot gnu.org 2022-09-29 2:00 ` cvs-commit at gcc dot gnu.org 2022-09-29 2:00 ` cvs-commit at gcc dot gnu.org 2022-09-29 2:34 ` cvs-commit at gcc dot gnu.org 2022-09-29 2:34 ` cvs-commit at gcc dot gnu.org 2022-09-29 2:35 ` cvs-commit at gcc dot gnu.org 2022-09-29 2:36 ` cvs-commit at gcc dot gnu.org 2022-09-29 2:36 ` cvs-commit at gcc dot gnu.org 2022-09-29 3:11 ` cvs-commit at gcc dot gnu.org 2022-09-29 3:11 ` cvs-commit at gcc dot gnu.org 2022-09-29 23:26 ` sam at gentoo dot org 2022-09-30 20:02 ` hjl.tools at gmail dot com 2022-10-01 15:23 ` aurelien at aurel32 dot net 2022-10-01 16:24 ` goldstein.w.n at gmail dot com 2022-10-01 16:51 ` goldstein.w.n at gmail dot com 2022-10-01 16:52 ` aurelien at aurel32 dot net 2022-10-03 21:46 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:46 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:47 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:47 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:47 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:47 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:47 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:51 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:51 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:51 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:51 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:51 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:51 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:51 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:55 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:55 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:55 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:56 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:56 ` cvs-commit at gcc dot gnu.org 2022-10-03 21:56 ` cvs-commit at gcc dot gnu.org 2022-10-03 22:02 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-03 22:02 ` cvs-commit at gcc dot gnu.org 2022-10-03 22:02 ` cvs-commit at gcc dot gnu.org 2022-10-03 22:02 ` cvs-commit at gcc dot gnu.org 2022-10-03 22:02 ` cvs-commit at gcc dot gnu.org 2022-10-03 22:02 ` cvs-commit at gcc dot gnu.org 2022-10-03 22:02 ` cvs-commit at gcc dot gnu.org 2022-10-03 22:05 ` cvs-commit at gcc dot gnu.org 2022-10-03 22:05 ` cvs-commit at gcc dot gnu.org 2022-10-03 22:05 ` cvs-commit at gcc dot gnu.org 2022-10-03 22:05 ` cvs-commit at gcc dot gnu.org 2022-10-03 22:05 ` cvs-commit at gcc dot gnu.org 2022-10-03 22:05 ` cvs-commit at gcc dot gnu.org 2022-10-04 5:05 ` aurelien at aurel32 dot net
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-29611-131-8mRsm7kB3r@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).