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:05:23 +0000 [thread overview] Message-ID: <bug-29611-131-4i7sare2SI@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 #65 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The release/2.33/master branch has been updated by Aurelien Jarno <aurel32@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=67e310afb91fa27295f7cf5140176efd6ba5dd51 commit 67e310afb91fa27295f7cf5140176efd6ba5dd51 Author: Aurelien Jarno <aurelien@aurel32.net> Date: Mon Oct 3 23:16:46 2022 +0200 x86-64: Require BMI1/BMI2 for AVX2 strrchr and wcsrchr implementations The AVX2 strrchr and wcsrchr implementation uses the 'blsmsk' instruction which belongs to the BMI1 CPU feature and the 'shrx' instruction, which belongs to the BMI2 CPU feature. Fixes: df7e295d18ff ("x86: Optimize {str|wcs}rchr-avx2") Partially resolves: BZ #29611 Reviewed-by: Noah Goldstein <goldstein.w.n@gmail.com> (cherry picked from commit 7e8283170c5d6805b609a040801d819e362a6292) -- 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:05 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 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 [this message] 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-4i7sare2SI@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).