public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/98856] [11 Regression] botan AES-128/XTS is slower by ~17% since r11-6649-g285fa338b06b804e72997c4d876ecf08a9c083af Date: Fri, 05 Mar 2021 10:43:47 +0000 [thread overview] Message-ID: <bug-98856-4-NAuj5HIO2I@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98856-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98856 --- Comment #26 from Richard Biener <rguenth at gcc dot gnu.org> --- (In reply to rguenther@suse.de from comment #25) > On Fri, 5 Mar 2021, ubizjak at gmail dot com wrote: > > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98856 > > > > --- Comment #24 from Uroš Bizjak <ubizjak at gmail dot com> --- > > (In reply to Richard Biener from comment #22) > > > I guess the idea of this insn setup was exactly to get IRA/LRA choose > > > the optimal instruction sequence - otherwise exposing the reload so > > > late is probably suboptimal. > > > > THere is one more tool in the toolbox. A peephole2 pattern can be > > conditionalized on availabe XMM register. So, if XMM reg is available, the > > GPR->XMM move can be emitted in front of the insn. So, if there is XMM register > > pressure, pinsrd will be used, but if an XMM register is availabe, it will be > > reused to emit punpcklqdq. > > > > The peephole2 pattern can also be conditionalized for targets where GPR->XMM > > moves are fast. > > Note the trick is esp. important when GPR->XMM moves are _slow_. But only > in the case we originally combine two GPR operands. Doing two > GPR->XMM moves and then one puncklqdq hides half of the latency of the > slow moves since they have no data dependence on each other. So for the > peephole we should try to match this - a reloaded operand and a GPR > operand. When the %xmm operand results from a SSE computation there's > no point in splitting out a GPR->XMM move. > > So in the end a peephole2 sounds like it could better match the condition > the transform is profitable on. I tried diff --git a/gcc/config/i386/sse.md b/gcc/config/i386/sse.md index db5be59f5b7..8d0d3077cf8 100644 --- a/gcc/config/i386/sse.md +++ b/gcc/config/i386/sse.md @@ -1419,6 +1419,23 @@ DONE; }) +(define_peephole2 + [(set (match_operand:DI 0 "sse_reg_operand") + (match_operand:DI 1 "general_gr_operand")) + (match_scratch:DI 2 "sse_reg_operand") + (set (match_operand:V2DI 2 "sse_reg_operand") + (vec_concat:V2DI (match_dup:DI 0) + (match_operand:DI 3 "general_gr_operand")))] + "reload_completed" + [(set (match_dup 0) + (match_dup 1)) + (set (match_dup 2) + (match_dup 3)) + (set (match_dup 2) + (vec_concat:V2DI (match_dup 0) + (match_dup 2)))] + "") + ;; Merge movsd/movhpd to movupd for TARGET_SSE_UNALIGNED_LOAD_OPTIMAL targets. (define_peephole2 [(set (match_operand:V2DF 0 "sse_reg_operand") but that doesn't seem to match for some unknown reason.
next prev parent reply other threads:[~2021-03-05 10:43 UTC|newest] Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-27 14:28 [Bug tree-optimization/98856] New: " marxin at gcc dot gnu.org 2021-01-27 14:29 ` [Bug tree-optimization/98856] " marxin at gcc dot gnu.org 2021-01-27 14:44 ` rguenth at gcc dot gnu.org 2021-01-28 7:47 ` rguenth at gcc dot gnu.org 2021-01-28 8:44 ` marxin at gcc dot gnu.org 2021-01-28 9:40 ` rguenth at gcc dot gnu.org 2021-01-28 11:03 ` rguenth at gcc dot gnu.org 2021-01-28 11:19 ` rguenth at gcc dot gnu.org 2021-01-28 11:57 ` rguenth at gcc dot gnu.org 2021-02-05 10:18 ` rguenth at gcc dot gnu.org 2021-02-05 11:52 ` jakub at gcc dot gnu.org 2021-02-05 12:52 ` rguenth at gcc dot gnu.org 2021-02-05 13:43 ` jakub at gcc dot gnu.org 2021-02-05 14:36 ` jakub at gcc dot gnu.org 2021-02-05 16:29 ` jakub at gcc dot gnu.org 2021-02-05 17:55 ` jakub at gcc dot gnu.org 2021-02-05 19:48 ` jakub at gcc dot gnu.org 2021-02-08 15:14 ` jakub at gcc dot gnu.org 2021-03-04 12:14 ` rguenth at gcc dot gnu.org 2021-03-04 15:36 ` rguenth at gcc dot gnu.org 2021-03-04 16:12 ` rguenth at gcc dot gnu.org 2021-03-04 17:56 ` ubizjak at gmail dot com 2021-03-04 18:12 ` ubizjak at gmail dot com 2021-03-05 7:44 ` rguenth at gcc dot gnu.org 2021-03-05 7:46 ` rguenth at gcc dot gnu.org 2021-03-05 8:29 ` ubizjak at gmail dot com 2021-03-05 10:04 ` rguenther at suse dot de 2021-03-05 10:43 ` rguenth at gcc dot gnu.org [this message] 2021-03-05 11:56 ` ubizjak at gmail dot com 2021-03-05 12:25 ` ubizjak at gmail dot com 2021-03-05 12:27 ` rguenth at gcc dot gnu.org 2021-03-05 12:49 ` jakub at gcc dot gnu.org 2021-03-05 12:52 ` ubizjak at gmail dot com 2021-03-05 12:55 ` rguenther at suse dot de 2021-03-05 13:06 ` rguenth at gcc dot gnu.org 2021-03-05 13:08 ` ubizjak at gmail dot com 2021-03-05 14:35 ` rguenth at gcc dot gnu.org 2021-03-08 10:41 ` rguenth at gcc dot gnu.org 2021-03-08 13:20 ` rguenth at gcc dot gnu.org 2021-03-08 15:46 ` amonakov at gcc dot gnu.org 2021-04-27 11:40 ` [Bug tree-optimization/98856] [11/12 " jakub at gcc dot gnu.org 2021-05-13 10:17 ` cvs-commit at gcc dot gnu.org 2021-07-28 7:05 ` rguenth at gcc dot gnu.org 2022-01-21 13:20 ` rguenth at gcc dot gnu.org 2022-04-21 7:48 ` rguenth at gcc dot gnu.org 2023-04-17 21:43 ` [Bug tree-optimization/98856] [11/12/13/14 " lukebenes at hotmail dot com 2023-04-18 9:07 ` rguenth at gcc dot gnu.org 2023-05-29 10:04 ` jakub 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-98856-4-NAuj5HIO2I@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).