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/102905] [12 regression] several vector test cases fail on power 7 after r12-4490 Date: Mon, 25 Oct 2021 06:40:00 +0000 [thread overview] Message-ID: <bug-102905-4-Cy7zqmwi07@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102905-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102905 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED Component|testsuite |tree-optimization Last reconfirmed| |2021-10-25 --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- As written in the commit log the existing code behaved odd and yes, possibly powerpc is the only target with weird enough costs to trigger this. The rev. definitely changed behavior in some way. I will see whether I can reproduce and adjust the thing according to my comment (where I was not sure whether it was worth the trouble - esp. without testsuite coverage ...).
next prev parent reply other threads:[~2021-10-25 6:40 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-22 18:56 [Bug testsuite/102905] New: " seurer at gcc dot gnu.org 2021-10-22 21:20 ` [Bug testsuite/102905] " pinskia at gcc dot gnu.org 2021-10-25 6:40 ` rguenth at gcc dot gnu.org [this message] 2021-10-25 9:33 ` [Bug tree-optimization/102905] " rguenth at gcc dot gnu.org 2021-10-25 10:49 ` cvs-commit at gcc dot gnu.org 2021-10-25 10:49 ` 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-102905-4-Cy7zqmwi07@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).