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 target/102473] [12 Regression] 521.wrf_r 5% slower at -Ofast and generic x86_64 tuning after r12-3426-g8f323c712ea76c Date: Fri, 24 Sep 2021 06:52:51 +0000 [thread overview] Message-ID: <bug-102473-4-nAsi1C06SO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102473-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102473 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Target Milestone|--- |12.0 Last reconfirmed| |2021-09-24 Summary|521.wrf_r 5% slower at |[12 Regression] 521.wrf_r |-Ofast and generic x86_64 |5% slower at -Ofast and |tuning after |generic x86_64 tuning after |r12-3426-g8f323c712ea76c |r12-3426-g8f323c712ea76c Ever confirmed|0 |1 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Looks like at least on Zen movs[hl]dup is on the integer domain so we'l see a domain crossing penalty here(?). But since this is a generic arch/tuning regression the SSE2 code path should be what matters - on the committed testcase I see foo: .LFB572: .cfi_startproc pxor %xmm0, %xmm0 addss (%rdi), %xmm0 addss 4(%rdi), %xmm0 addss 8(%rdi), %xmm0 addss 12(%rdi), %xmm0 ret where it seems that the vectorizer doesn't pick up the reduction pattern. /home/rguenther/src/gcc2/gcc/testsuite/gcc.target/i386/sse2-pr101059.c:20:21: note: vect_is_simple_use: vectype vector(4) float /home/rguenther/src/gcc2/gcc/testsuite/gcc.target/i386/sse2-pr101059.c:20:21: missed: reduc op not supported by target.
next prev parent reply other threads:[~2021-09-24 6:52 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-23 16:45 [Bug target/102473] New: " jamborm at gcc dot gnu.org 2021-09-24 6:52 ` rguenth at gcc dot gnu.org [this message] 2021-09-24 7:39 ` [Bug target/102473] [12 Regression] " crazylht at gmail dot com 2021-09-24 7:50 ` rguenth at gcc dot gnu.org 2021-09-24 10:43 ` crazylht at gmail dot com 2021-09-26 7:29 ` crazylht at gmail dot com 2021-09-27 2:01 ` crazylht at gmail dot com 2021-09-27 2:16 ` crazylht at gmail dot com 2021-09-27 7:49 ` crazylht at gmail dot com 2021-09-27 7:51 ` cvs-commit at gcc dot gnu.org 2021-09-27 8:10 ` jamborm at gcc dot gnu.org 2021-09-27 8:18 ` crazylht at gmail dot com 2021-09-27 14:27 ` hjl.tools at gmail dot com 2021-09-28 2:20 ` crazylht at gmail dot com 2021-09-28 2:24 ` hjl.tools at gmail dot com 2021-09-28 2:59 ` crazylht at gmail dot com 2022-01-20 9:53 ` rguenth at gcc dot gnu.org 2022-05-06 8:31 ` [Bug target/102473] [12/13 " jakub at gcc dot gnu.org 2022-07-26 13:27 ` 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-102473-4-nAsi1C06SO@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).