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: Thu, 04 Mar 2021 12:14:22 +0000 [thread overview] Message-ID: <bug-98856-4-H0yX72NteN@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 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |vmakarov at gcc dot gnu.org Keywords| |ra --- Comment #17 from Richard Biener <rguenth at gcc dot gnu.org> --- So coming back here. We're presenting RA with a quite hard problem given we have (insn 7 4 8 2 (set (reg:TI 84 [ _9 ]) (mem:TI (reg:DI 101) [0 MEM <__int128 unsigned> [(char * {ref-all})in_8(D)]+0 S16 A8])) 73 {*movti_internal} (expr_list:REG_DEAD (reg:DI 101) (nil))) (insn 8 7 9 2 (parallel [ (set (reg:DI 95) (lshiftrt:DI (subreg:DI (reg:TI 84 [ _9 ]) 8) (const_int 63 [0x3f]))) (clobber (reg:CC 17 flags)) ]) "t.c":7:26 703 {*lshrdi3_1} (expr_list:REG_UNUSED (reg:CC 17 flags) (nil))) .. (insn 10 9 11 2 (parallel [ (set (reg:DI 97) (lshiftrt:DI (subreg:DI (reg:TI 84 [ _9 ]) 0) (const_int 63 [0x3f]))) (clobber (reg:CC 17 flags)) ]) "t.c":8:30 703 {*lshrdi3_1} (expr_list:REG_UNUSED (reg:CC 17 flags) .. (insn 12 11 13 2 (set (reg:V2DI 98 [ vect__5.3 ]) (ashift:V2DI (subreg:V2DI (reg:TI 84 [ _9 ]) 0) (const_int 1 [0x1]))) "t.c":9:16 3611 {ashlv2di3} (expr_list:REG_DEAD (reg:TI 84 [ _9 ]) (nil))) where I wonder why we keep the (subreg:DI (reg:TI 84 ...) 8) around for so long. Probably the subreg pass gives up because of the V2DImode subreg of that reg. That said RA chooses xmm for reg:84 but then spills it immediately to fulfil the subregs even though there's mov and pextrd that could be used or the reload could use the original mem. That we reload even the xmm use is another odd thing. Vlad, I'm not sure about the possibilities LRA has here but maybe you can have a look at the testcase in comment#6 (use -O3 -march=znver2 or -march=core-avx2). For one I expected vmovdqu (%rsi), %xmm2 vmovdqa %xmm2, -24(%rsp) movq -16(%rsp), %rax (2a) vmovdqa -24(%rsp), %xmm4 (1) ... movq -24(%rsp), %rdx (2b) (1) to be not there (not sure how that even survives postreload optimizations...) (2a/b) to be 'inherited' by instead loading from (%rsi) and 8(%rsi) which is maybe too much being asked because it requires aliasing considerations That is, even if we don't consider using movq %xmm2, %rax (2a) pextrd %xmm2, %rdx, 1 (2b) I expected us to not spill.
next prev parent reply other threads:[~2021-03-04 12:14 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 [this message] 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 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-H0yX72NteN@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).