public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jiangchuanganghw at outlook dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/114468] New: unixbench compilation performance results vary with different gcc compilers
Date: Mon, 25 Mar 2024 13:31:16 +0000	[thread overview]
Message-ID: <bug-114468-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 114468
           Summary: unixbench compilation performance results vary with
                    different gcc compilers
           Product: gcc
           Version: 10.3.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jiangchuanganghw at outlook dot com
  Target Milestone: ---

We used Unixbench to compare gcc 10.3.0 with gcc8.5 on an intel Sapphire Rapids
CPU and found that the performance of the dhry2reg test project compiled with
gcc 10.3.0 deteriorated by about 10%. We found that this commit affected
performance, and after rolling back the changes in that patch, performance was
restored.
https://github.com/gcc-mirror/gcc/commit/3133bed5d0327e8a9cd0a601b7ecdb9de4fc825d

We expect to find the cause of this result.Looking forward to your help.

             reply	other threads:[~2024-03-25 13:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 13:31 jiangchuanganghw at outlook dot com [this message]
2024-03-25 14:01 ` [Bug target/114468] " pinskia at gcc dot gnu.org
2024-03-25 15:16 ` rguenth at gcc dot gnu.org
2024-03-25 23:25 ` [Bug target/114468] unixbench compilation performance results vary with different gcc compilers (r10-6804-g3133bed5d0327e) pinskia 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-114468-4@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).