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 middle-end/88873] missing vectorization for decomposed operations on a vector type Date: Wed, 12 Jul 2023 11:33:04 +0000 [thread overview] Message-ID: <bug-88873-4-QF8IIJEMA9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-88873-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88873 --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> --- Didn't yet help for the original testcase in the description. We RTL expand from vect__1.11_14 = MEM <vector(2) double> [(double *)&c]; vect__2.5_12 = MEM <vector(2) double> [(double *)&b]; vect__3.8_13 = MEM <vector(2) double> [(double *)&a]; vect__4.12_15 = .FMA (vect__2.5_12, vect__3.8_13, vect__1.11_14); MEM <vector(2) double> [(double *)&D.4349] = vect__4.12_15; return D.4349; and get (insn 2 21 3 2 (set (reg:DF 91) (reg:DF 20 xmm0 [ a ])) "t.c":8:1 -1 (nil)) (insn 3 2 4 2 (set (reg:DF 92) (reg:DF 21 xmm1 [ a+8 ])) "t.c":8:1 -1 (nil)) (insn 4 3 5 2 (set (reg:TI 90) (const_int 0 [0])) "t.c":8:1 -1 (nil)) (insn 5 4 6 2 (set (subreg:DF (reg:TI 90) 0) (reg:DF 91)) "t.c":8:1 -1 (nil)) (insn 6 5 7 2 (set (subreg:DF (reg:TI 90) 8) (reg:DF 92)) "t.c":8:1 -1 (nil)) (insn 7 6 8 2 (set (reg/v:TI 89 [ a ]) (reg:TI 90)) "t.c":8:1 -1 (nil)) ... (insn 23 20 24 2 (set (reg:V2DF 85 [ vect__4.12 ]) (fma:V2DF (subreg:V2DF (reg/v:TI 93 [ b ]) 0) (subreg:V2DF (reg/v:TI 89 [ a ]) 0) (subreg:V2DF (reg/v:TI 97 [ c ]) 0))) "t.c":9:18 -1 (nil)) so the ABI passess struct s_t in two %xmm regs but the backend gives it TImode. Nothing cleans this up, we end up with horrible code in the end. The subreg pass is likely "confused" by the V2DFmode subreg of the TImode pseudos, maybe it needs to learn to turn the TImode pseudo into a V2DFmode one ...
next prev parent reply other threads:[~2023-07-12 11:33 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-88873-4@http.gcc.gnu.org/bugzilla/> 2021-08-21 21:25 ` [Bug tree-optimization/88873] " pinskia at gcc dot gnu.org 2023-06-21 13:33 ` [Bug middle-end/88873] " rguenth at gcc dot gnu.org 2023-06-21 22:18 ` roger at nextmovesoftware dot com 2023-07-10 8:09 ` cvs-commit at gcc dot gnu.org 2023-07-12 11:33 ` rguenth at gcc dot gnu.org [this message] 2023-07-14 17:13 ` cvs-commit at gcc dot gnu.org 2023-07-20 8:25 ` cvs-commit at gcc dot gnu.org 2023-08-04 15:24 ` cvs-commit 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-88873-4-QF8IIJEMA9@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).