public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub 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: Fri, 12 Feb 2021 11:18:55 +0000 [thread overview]
Message-ID: <bug-96166-4-dLFd3BTLuh@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
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |uros at gcc dot gnu.org
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
So perhaps a peephole2 that matches
(insn 15 6 9 2 (set (reg:V2SI 21 xmm1 [91])
(mem:V2SI (reg/v/f:DI 5 di [orig:86 x ] [86]) [0 MEM <long unsigned
int> [(char * {ref-all})x_2(D)]+0 S8 A8])) "pr96166.c":13:19 1288
{*movv2si_internal}
(nil))
(insn 9 15 10 2 (set (reg:V2SI 20 xmm0 [88])
(vec_select:V2SI (reg:V2SI 21 xmm1 [91])
(parallel [
(const_int 1 [0x1])
(const_int 0 [0])
]))) "pr96166.c":13:19 1410 {*mmx_pshufd_1}
(expr_list:REG_DEAD (reg:V2SI 21 xmm1 [91])
(expr_list:REG_EQUIV (mem:V2SI (reg/v/f:DI 5 di [orig:86 x ] [86]) [0
MEM <long unsigned int> [(char * {ref-all})x_2(D)]+0 S8 A8])
(nil))))
(insn 10 9 17 2 (set (mem:V2SI (reg/v/f:DI 5 di [orig:86 x ] [86]) [0 MEM <long
unsigned int> [(char * {ref-all})x_2(D)]+0 S8 A8])
(reg:V2SI 20 xmm0 [88])) "pr96166.c":13:19 1288 {*movv2si_internal}
(expr_list:REG_DEAD (reg:V2SI 20 xmm0 [88])
(expr_list:REG_DEAD (reg/v/f:DI 5 di [orig:86 x ] [86])
(nil))))
back into the rotate of the MEM?
No other ideas on my side :(
next prev parent reply other threads:[~2021-02-12 11:18 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 [this message]
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
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-dLFd3BTLuh@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: link
Be 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).