public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/96337] [10/11 Regression] GCC 10.2: twice as slow for -O2 -march=x86-64 vs. GCC 9.3/8.4 Date: Sat, 19 Sep 2020 21:34:45 +0000 [thread overview] Message-ID: <bug-96337-4-s4nXjWtwuY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96337-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96337 Jan Hubicka <hubicka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #16 from Jan Hubicka <hubicka at gcc dot gnu.org> --- It seems that the benchmarks was flawed. We could reopen if phoronix suceeds to reporduce them.
next prev parent reply other threads:[~2020-09-19 21:34 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-27 15:32 [Bug rtl-optimization/96337] New: " aros at gmx dot com 2020-07-27 18:36 ` [Bug rtl-optimization/96337] " david.bolvansky at gmail dot com 2020-07-27 21:13 ` aros at gmx dot com 2020-07-28 6:04 ` [Bug ipa/96337] [10/11 Regression] " rguenth at gcc dot gnu.org 2020-07-28 6:04 ` rguenth at gcc dot gnu.org 2020-07-28 6:20 ` hubicka at gcc dot gnu.org 2020-07-28 6:42 ` hubicka at gcc dot gnu.org 2020-07-28 6:49 ` hubicka at gcc dot gnu.org 2020-07-28 8:08 ` hubicka at gcc dot gnu.org 2020-07-28 8:24 ` hubicka at gcc dot gnu.org 2020-07-28 8:39 ` hubicka at gcc dot gnu.org 2020-07-28 8:47 ` david.bolvansky at gmail dot com 2020-07-28 9:37 ` Jan Hubicka 2020-07-28 9:37 ` hubicka at ucw dot cz 2020-07-29 7:56 ` aros at gmx dot com 2020-08-01 18:53 ` andysem at mail dot ru 2020-08-01 19:30 ` Jan Hubicka 2020-08-01 19:14 ` david.bolvansky at gmail dot com 2020-08-01 19:30 ` hubicka at ucw dot cz 2020-09-19 21:34 ` hubicka at gcc dot gnu.org [this message] 2020-09-19 21:39 ` vz-gcc at zeitlins dot org 2020-09-19 21:46 ` hubicka at ucw dot cz 2020-09-19 21:49 ` vz-gcc at zeitlins dot org 2020-09-19 21:52 ` hubicka at ucw dot cz
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-96337-4-s4nXjWtwuY@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).