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/114238] [14 regression] Multiple 554.roms_r run-time regressions (4%-20%) since r14-9193-ga0b1798042d033 Date: Fri, 08 Mar 2024 14:03:51 +0000 [thread overview] Message-ID: <bug-114238-4-Pu1hTjNfbt@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114238-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114238 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- r14-9391-g018ddc86b92851 fixed this on Zen2 for me as well.
next prev parent reply other threads:[~2024-03-08 14:03 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-05 13:03 [Bug tree-optimization/114238] New: " jamborm at gcc dot gnu.org 2024-03-07 5:00 ` [Bug tree-optimization/114238] [14 regression] " pinskia at gcc dot gnu.org 2024-03-07 20:37 ` law at gcc dot gnu.org 2024-03-08 14:03 ` rguenth at gcc dot gnu.org [this message] 2024-03-12 7:18 ` haochen.jiang at intel dot com
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-114238-4-Pu1hTjNfbt@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).