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 regression/103318] New: Spec 2017 benchmark perlbench_r fails on PowerPC for -Ofast and -O3, passes with -O2
Date: Thu, 18 Nov 2021 16:13:25 +0000	[thread overview]
Message-ID: <bug-103318-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 103318
           Summary: Spec 2017 benchmark perlbench_r fails on PowerPC for
                    -Ofast and -O3, passes with -O2
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: regression
          Assignee: unassigned at gcc dot gnu.org
          Reporter: meissner at gcc dot gnu.org
  Target Milestone: ---

The Spec 2017 benchmark perlbench_r compiles fine but produces the wrong output
when compiled with -O3 or -Ofast options on both power9 and power10.  Using -O2
produces the right results on power10.  In going back with the previous runs
that I've done on power10, it worked with sources checked out on October 17th,
but failed with sources checked out on November 4th and November 17th.

For power10, the options that I use are:
-g -mlittle -save-temps=obj -ffast-math -Ofast -mcpu=power10 -mrecip \
-funroll-loops -m64  -fgnu89-inline -Wno-multichar -DSPEC_LP64 \
-frandom-seed=spec2017 -D_XOPEN_SOURCE=500 -DSPEC_LINUX_PPC_LE \
-fno-strict-aliasing -std=gnu11 -Wno-builtin-macro-redefined -w

             reply	other threads:[~2021-11-18 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 16:13 meissner at gcc dot gnu.org [this message]
2021-11-18 16:14 ` [Bug regression/103318] " meissner at gcc dot gnu.org
2021-11-18 16:32 ` meissner at gcc dot gnu.org
2021-11-19  8:14 ` rguenth at gcc dot gnu.org
2024-05-02 21:31 ` 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-103318-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).