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/114057] [14 Regression] 435.gromacs fails verification with -Ofast -march={znver2,znver4} and PGO after r14-7272-g57f611604e8bab Date: Tue, 26 Mar 2024 10:59:41 +0000 [thread overview] Message-ID: <bug-114057-4-LoOXfGbCBv@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114057-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114057 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu.org --- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> --- I guess that bisecting with -fno-vect-cost-model might reveal the actual offender. (if it doesn't turn up other problems, of course)
next prev parent reply other threads:[~2024-03-26 10:59 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-22 16:19 [Bug target/114057] New: [14 Regression] 435.gromacs fails verification on with -Ofast -march=znver4 and PGO pheeck at gcc dot gnu.org 2024-02-22 17:50 ` [Bug target/114057] " pheeck at gcc dot gnu.org 2024-02-22 18:08 ` pheeck at gcc dot gnu.org 2024-02-23 6:54 ` rguenth at gcc dot gnu.org 2024-02-23 9:44 ` pheeck at gcc dot gnu.org 2024-02-23 10:26 ` [Bug tree-optimization/114057] [14 Regression] 435.gromacs fails verification with -Ofast -march=znver4 and PGO after r14-7272-g57f611604e8bab pheeck at gcc dot gnu.org 2024-02-25 11:11 ` [Bug tree-optimization/114057] [14 Regression] 435.gromacs fails verification with -Ofast -march={znver2,znver4} " pheeck at gcc dot gnu.org 2024-03-07 20:38 ` law at gcc dot gnu.org 2024-03-26 10:59 ` rguenth at gcc dot gnu.org [this message] 2024-03-26 11:27 ` rguenth at gcc dot gnu.org 2024-03-26 12:02 ` rguenth at gcc dot gnu.org 2024-03-26 15:32 ` rguenth at gcc dot gnu.org 2024-03-26 15:34 ` rguenth at gcc dot gnu.org 2024-03-26 15:35 ` rguenth at gcc dot gnu.org 2024-03-27 10:36 ` rguenth at gcc dot gnu.org 2024-03-27 11:50 ` cvs-commit at gcc dot gnu.org 2024-03-27 11:51 ` rguenth at gcc dot gnu.org 2024-03-28 7:04 ` 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-114057-4-LoOXfGbCBv@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).