public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "edlinger at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/94472] 400.perlbench is slower when compiled at -O2 with both PGO and LTO on AMD Zen CPUs
Date: Tue, 28 Apr 2020 08:36:43 +0000	[thread overview]
Message-ID: <bug-94472-4-hxDl3Wbpxw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94472-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94472

--- Comment #4 from Bernd Edlinger <edlinger at gcc dot gnu.org> ---
(In reply to Martin Jambor from comment #3)
> My benchmarking setup is currently gone so unfortunately no, not easily. 
> I'll be re-measuring everything on a different computer with a slightly
> different CPU model soon, so after that I guess I could.  But it is most
> likely the limits, yes.

Yeah, easy to fix, but it takes some time.
But this is not more important than your life.

Shall I raise this to P1 so it prevents gcc-10 release?

  parent reply	other threads:[~2020-04-28  8:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 14:54 [Bug gcov-profile/94472] New: " jamborm at gcc dot gnu.org
2020-04-28  2:30 ` [Bug ipa/94472] " edlinger at gcc dot gnu.org
2020-04-28  2:36 ` edlinger at gcc dot gnu.org
2020-04-28  8:06 ` jamborm at gcc dot gnu.org
2020-04-28  8:36 ` edlinger at gcc dot gnu.org [this message]
2020-04-28  8:38 ` jakub at gcc dot gnu.org
2020-04-28  8:41 ` edlinger at gcc dot gnu.org
2020-04-28  8:42 ` edlinger at gcc dot gnu.org
2020-04-28  9:21 ` rguenth at gcc dot gnu.org
2020-04-28  9:22 ` rguenth at gcc dot gnu.org
2020-04-28  9:57 ` hubicka at ucw dot cz
2020-04-28 13:09 ` edlinger 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-94472-4-hxDl3Wbpxw@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: link
Be 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).