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/96166] [10/11 Regression] -O3/-ftree-slp-vectorize turns ROL into a mess Date: Sat, 13 Feb 2021 09:33:14 +0000 [thread overview] Message-ID: <bug-96166-4-HMmvgWoS0h@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96166-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96166 --- Comment #11 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:0f3a743b688f4845e1798eed9b2e2284e891da11 commit r11-7233-g0f3a743b688f4845e1798eed9b2e2284e891da11 Author: Jakub Jelinek <jakub@redhat.com> Date: Sat Feb 13 10:32:16 2021 +0100 i386: Add combiner splitter to optimize V2SImode memory rotation [PR96166] Since the x86 backend enabled V2SImode vectorization (with TARGET_MMX_WITH_SSE), slp vectorization can kick in and emit movq (%rdi), %xmm1 pshufd $225, %xmm1, %xmm0 movq %xmm0, (%rdi) instead of rolq $32, (%rdi) we used to emit (or emit when slp vectorization is disabled). I think the rotate is both smaller and faster, so this patch adds a combiner splitter to optimize that back. 2021-02-13 Jakub Jelinek <jakub@redhat.com> PR target/96166 * config/i386/mmx.md (*mmx_pshufd_1): Add a combine splitter for swap of V2SImode elements in memory into DImode memory rotate by 32. * gcc.target/i386/pr96166.c: New test.
next prev parent reply other threads:[~2021-02-13 9:33 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-11 16:01 [Bug tree-optimization/96166] New: " nok.raven at gmail dot com 2020-07-13 8:05 ` [Bug target/96166] " rguenth at gcc dot gnu.org 2020-07-23 6:51 ` rguenth at gcc dot gnu.org 2020-10-12 12:47 ` rguenth at gcc dot gnu.org 2021-02-11 15:00 ` jakub at gcc dot gnu.org 2021-02-12 10:11 ` jakub at gcc dot gnu.org 2021-02-12 11:18 ` jakub at gcc dot gnu.org 2021-02-12 12:17 ` pinskia at gcc dot gnu.org 2021-02-12 12:21 ` jakub at gcc dot gnu.org 2021-02-12 13:53 ` jakub at gcc dot gnu.org 2021-02-12 14:03 ` rguenth at gcc dot gnu.org 2021-02-12 14:40 ` jakub at gcc dot gnu.org 2021-02-13 9:33 ` cvs-commit at gcc dot gnu.org [this message] 2021-02-13 9:34 ` [Bug target/96166] [10 " jakub at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2022-06-28 10:41 ` jakub at gcc dot gnu.org 2023-07-07 8:55 ` rguenth at gcc dot gnu.org
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-96166-4-HMmvgWoS0h@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).