public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99405] Rotate with mask not optimized on x86 for QI/HImode rotates Date: Tue, 27 Apr 2021 08:18:33 +0000 [thread overview] Message-ID: <bug-99405-4-UXUFimYyEC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99405-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99405 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:71c8aaf29bb122ebe5e67c84903fd23ff05f04ec commit r12-140-g71c8aaf29bb122ebe5e67c84903fd23ff05f04ec Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Apr 27 10:17:45 2021 +0200 i386: Improve [QH]Imode rotates with masked shift count [PR99405] The following testcase shows that while we nicely optimize away the useless and? of shift count before rotation for [SD]Imode rotates, we don't do that for [QH]Imode. The following patch optimizes that by using the right iterator on those 4 patterns. 2021-04-27 Jakub Jelinek <jakub@redhat.com> PR target/99405 * config/i386/i386.md (*<insn><mode>3_mask, *<insn><mode>3_mask_1): For any_rotate define_insn_split and following splitters, use SWI iterator instead of SWI48. * gcc.target/i386/pr99405.c: New test.
next prev parent reply other threads:[~2021-04-27 8:18 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-05 12:38 [Bug target/99405] New: " jakub at gcc dot gnu.org 2021-03-05 12:43 ` [Bug target/99405] " jakub at gcc dot gnu.org 2021-03-05 12:59 ` ubizjak at gmail dot com 2021-03-05 13:03 ` jakub at gcc dot gnu.org 2021-03-05 14:55 ` unlvsur at live dot com 2021-03-05 14:59 ` jakub at gcc dot gnu.org 2021-03-05 15:06 ` unlvsur at live dot com 2021-03-06 10:13 ` jakub at gcc dot gnu.org 2021-04-27 8:18 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-27 18:43 ` roger at nextmovesoftware 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-99405-4-UXUFimYyEC@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).