public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/98119] SVE: Wrong code with -O1 -ftree-vectorize -msve-vector-bits=512 -mtune=thunderx Date: Thu, 03 Dec 2020 13:06:09 +0000 [thread overview] Message-ID: <bug-98119-4-m5YtgBeOkd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98119-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98119 rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2020-12-03 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> --- Confirmed. I think this is likely to be a bad interaction between unpacked vectors and the optimisation to use predication when peeling for alignment. It's really an optimisation/cost model bug that we used unpacked stores for this testcase at all, but given that we do, the number of peeled iterations is being calculated incorrectly.
next prev parent reply other threads:[~2020-12-03 13:06 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-03 12:20 [Bug target/98119] New: " acoplan at gcc dot gnu.org 2020-12-03 13:06 ` rsandifo at gcc dot gnu.org [this message] 2020-12-07 9:32 ` [Bug target/98119] [10/11 Regression] " acoplan at gcc dot gnu.org 2020-12-07 12:45 ` rguenth at gcc dot gnu.org 2021-01-14 11:00 ` rguenth at gcc dot gnu.org 2021-03-30 15:06 ` rsandifo at gcc dot gnu.org 2021-03-31 10:26 ` cvs-commit at gcc dot gnu.org 2021-03-31 20:39 ` [Bug target/98119] [10 " rsandifo at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2021-04-23 16:17 ` cvs-commit at gcc dot gnu.org 2021-04-23 16:19 ` rsandifo 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-98119-4-m5YtgBeOkd@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).