public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/103498] New: Spec 2017 imagick_r is 2.62% slower on Power10 with pc-relative addressing compared to not using pc-relative addressing
Date: Tue, 30 Nov 2021 16:14:08 +0000	[thread overview]
Message-ID: <bug-103498-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 103498
           Summary: Spec 2017 imagick_r is 2.62% slower on Power10 with
                    pc-relative addressing compared to not using
                    pc-relative addressing
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: meissner at gcc dot gnu.org
  Target Milestone: ---

I was doing some Spec 2017 rate runs on a single power10 little endian 64-bit
CPU.  One of the runs disabled pc-relative addressing.  One benchmark
(imagick_r) was faster if PC-relative addressing was disabled.

For this run I used the options:
    -DSPEC \
    -DNDEBUG \
    -I. \
    -DSPEC_AUTO_SUPPRESS_OPENMP \
    -g \
    -save-temps=obj \
    -Ofast \
    -mcpu=power10 \
    -mrecip \
    -funroll-loops \
    -msave-toc-indirect \
    -mno-pcrel \
    -fgnu89-inline \
    -Wno-multichar \
    -DSPEC_LP64 \
    -frandom-seed=spec2017

             reply	other threads:[~2021-11-30 16:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30 16:14 meissner at gcc dot gnu.org [this message]
2022-08-09  6:42 ` [Bug target/103498] " guihaoc at gcc dot gnu.org
2022-08-09  9:26 ` segher at gcc dot gnu.org
2023-06-02  3:31 ` bergner at gcc dot gnu.org
2023-06-02  4:40 ` meissner 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-103498-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).