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/99412] s352 benchmark of TSVC is vectorized by clang and not by gcc Date: Mon, 08 Mar 2021 08:32:46 +0000 [thread overview] Message-ID: <bug-99412-4-ceMZeBXHzi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99412-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99412 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|middle-end |tree-optimization Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Blocks| |53947 Keywords| |missed-optimization Ever confirmed|0 |1 Depends on| |97832 Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2021-03-08 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- With -fno-tree-reassoc we detect the reduction chain and produce .L3: vmovaps b(%rax), %ymm5 vmovaps b+32(%rax), %ymm6 addq $160, %rax vfmadd231ps a-160(%rax), %ymm5, %ymm1 vmovaps b-96(%rax), %ymm7 vfmadd231ps a-128(%rax), %ymm6, %ymm0 vmovaps b-64(%rax), %ymm5 vmovaps b-32(%rax), %ymm6 vfmadd231ps a-96(%rax), %ymm7, %ymm2 vfmadd231ps a-64(%rax), %ymm5, %ymm3 vfmadd231ps a-32(%rax), %ymm6, %ymm4 cmpq $128000, %rax jne .L3 vaddps %ymm1, %ymm0, %ymm0 vaddps %ymm2, %ymm0, %ymm0 vaddps %ymm3, %ymm0, %ymm0 vaddps %ymm4, %ymm0, %ymm0 vextractf128 $0x1, %ymm0, %xmm1 vaddps %xmm0, %xmm1, %xmm1 vmovhlps %xmm1, %xmm1, %xmm0 vaddps %xmm1, %xmm0, %xmm0 vshufps $85, %xmm0, %xmm0, %xmm1 vaddps %xmm0, %xmm1, %xmm0 decl %edx jne .L2 we're not re-rolling and thus are forced to use a VF of 4 here. Note that LLVM doesn't seem to veectorize the loop but instead vectorizes the basic-block which isn't what TSVC looks for (but that would work for non-fast-math). Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947 [Bug 53947] [meta-bug] vectorizer missed-optimizations https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97832 [Bug 97832] AoSoA complex caxpy-like loops: AVX2+FMA -Ofast 7 times slower than -O3
next prev parent reply other threads:[~2021-03-08 8:32 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-05 14:54 [Bug middle-end/99412] New: " hubicka at gcc dot gnu.org 2021-03-08 8:32 ` rguenth at gcc dot gnu.org [this message] 2021-06-09 12:54 ` [Bug tree-optimization/99412] " rguenth at gcc dot gnu.org 2023-01-11 19:14 ` hubicka at gcc dot gnu.org 2023-01-12 9:12 ` rguenth at gcc dot gnu.org 2023-01-12 9:30 ` rguenth at gcc dot gnu.org 2023-01-12 13:30 ` cvs-commit at gcc dot gnu.org 2023-01-12 13:42 ` rguenth at gcc dot gnu.org 2023-01-12 13:42 ` 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-99412-4-ceMZeBXHzi@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).