public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "admin at levyhsu dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107563] __builtin_shufflevector fails to pshufd instructions under default x86_64 compilation toggle which is the sse2 one Date: Sat, 18 May 2024 15:17:12 +0000 [thread overview] Message-ID: <bug-107563-4-DWJ5uDDJY9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107563-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107563 --- Comment #12 from Levy Hsu <admin at levyhsu dot com> --- switch (d->vmode) { case E_V8QImode: if (!TARGET_MMX_WITH_SSE) return false; mode = V4HImode; gen_shr = gen_ashrv4hi3(should be gen_lshrv4hi3); gen_shl = gen_ashlv4hi3; gen_or = gen_iorv4hi3; break; case E_V16QImode: mode = V8HImode; gen_shr = gen_vlshrv8hi3; gen_shl = gen_vashlv8hi3; gen_or = gen_iorv8hi3; break; default: return false; } Obviously, under V8QImode it should be gen_lshrv4hi3 instead of gen_ashrv4hi3. I mistakenly used gen_ashrv4hi3 due to the similar naming conventions and failed to find out. gen_lshrv4hi3 is the correct logical shift needed. Will send a patch soon
prev parent reply other threads:[~2024-05-18 15:17 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-07 22:56 [Bug rtl-optimization/107563] New: __builtin_shufflevector fails to use pshufb and " unlvsur at live dot com 2022-11-07 23:00 ` [Bug target/107563] " unlvsur at live dot com 2022-11-07 23:05 ` [Bug target/107563] __builtin_shufflevector fails to " unlvsur at live dot com 2022-11-08 0:11 ` unlvsur at live dot com 2022-11-08 0:11 ` unlvsur at live dot com 2022-11-08 3:23 ` crazylht at gmail dot com 2022-11-08 3:33 ` crazylht at gmail dot com 2022-11-08 6:11 ` unlvsur at live dot com 2022-11-08 6:11 ` unlvsur at live dot com 2022-11-08 6:14 ` unlvsur at live dot com 2022-11-08 8:28 ` crazylht at gmail dot com 2024-05-15 4:47 ` cvs-commit at gcc dot gnu.org 2024-05-18 15:17 ` admin at levyhsu dot com [this message]
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-107563-4-DWJ5uDDJY9@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).