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/104058] [12 Regression] 6-7% x264_r regression with -march=native -Ofast -funroll-loops -flto on x86 since r12-6420-gd3ff7420e941931d32ce2e332e7968fe67ba20af Date: Tue, 18 Jan 2022 13:46:02 +0000 [thread overview] Message-ID: <bug-104058-4-0tEux5OKQA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104058-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104058 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING Depends on| |103997 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- Waiting for the PR103997 fix, please re-evaluate after that bug is closed. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103997 [Bug 103997] [12 Regression] gcc.target/i386/pr88531-??.c scan-assembler-times FAILs
next prev parent reply other threads:[~2022-01-18 13:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-17 2:04 [Bug tree-optimization/104058] New: " admin at levyhsu dot com 2022-01-17 2:07 ` [Bug tree-optimization/104058] " pinskia at gcc dot gnu.org 2022-01-17 2:10 ` pinskia at gcc dot gnu.org 2022-01-17 8:39 ` rguenth at gcc dot gnu.org 2022-01-17 10:45 ` marxin at gcc dot gnu.org 2022-01-18 13:46 ` rguenth at gcc dot gnu.org [this message] 2022-01-20 8:51 ` admin at levyhsu dot com 2022-01-25 11:02 ` 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-104058-4-0tEux5OKQA@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).