public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/96750] 10-12% performance decrease in benchmark going from GCC8 to GCC9/GCC10 Date: Mon, 24 Aug 2020 08:47:16 +0000 [thread overview] Message-ID: <bug-96750-4-NAFNqQsjyp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96750-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96750 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2020-08-24 CC| |hubicka at gcc dot gnu.org, | |marxin at gcc dot gnu.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- Confirmed, started with r9-5763-g61a8637c8893a252: after: 1794240.0 before: 1802710.0 Anyway, using PGO one can get to: 1488310.0
next prev parent reply other threads:[~2020-08-24 8:47 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-23 6:03 [Bug c++/96750] New: " mattreecebentley at gmail dot com 2020-08-24 8:47 ` marxin at gcc dot gnu.org [this message] 2020-08-24 9:17 ` [Bug middle-end/96750] " glisse at gcc dot gnu.org 2020-08-24 9:38 ` marxin at gcc dot gnu.org 2020-08-24 23:21 ` mattreecebentley at gmail dot com 2020-09-27 23:34 ` mattreecebentley at gmail dot com 2020-09-27 23:35 ` mattreecebentley at gmail dot com 2021-12-22 10:41 ` [Bug ipa/96750] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org 2022-01-21 13:27 ` rguenth at gcc dot gnu.org 2022-05-27 9:43 ` [Bug ipa/96750] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:41 ` jakub at gcc dot gnu.org 2022-10-19 9:21 ` rguenth at gcc dot gnu.org 2022-10-19 9:22 ` rguenth at gcc dot gnu.org 2023-07-07 10:37 ` [Bug ipa/96750] [11/12/13/14 " 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-96750-4-NAFNqQsjyp@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).