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 tree-optimization/98854] New: [11 Regression] cray benchmark is about 15% slower since r11-4428-g4a369d199bf2f34e
Date: Wed, 27 Jan 2021 12:45:14 +0000	[thread overview]
Message-ID: <bug-98854-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 98854
           Summary: [11 Regression] cray benchmark is about 15% slower
                    since r11-4428-g4a369d199bf2f34e
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: rguenth at gcc dot gnu.org
  Target Milestone: ---

Since the revision, the following is slower on znver2:

$ make clean && m CFLAGS="-Ofast -march=znver2 -g" && cat sphfract | ./c-ray-mt
-o /dev/null
c-ray-mt v1.1
Rendering took: 1 seconds (1798 milliseconds)

while GCC 10 has:

c-ray-mt v1.1
Rendering took: 1 seconds (1585 milliseconds)

             reply	other threads:[~2021-01-27 12:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 12:45 marxin at gcc dot gnu.org [this message]
2021-01-27 12:46 ` [Bug tree-optimization/98854] " marxin at gcc dot gnu.org
2021-01-27 13:13 ` rguenth at gcc dot gnu.org
2021-01-27 13:46 ` rguenth at gcc dot gnu.org
2021-01-27 14:22 ` rguenth at gcc dot gnu.org
2021-01-27 14:39 ` marxin at gcc dot gnu.org
2021-01-27 14:45 ` rguenther at suse dot de
2021-01-27 14:52 ` marxin at gcc dot gnu.org
2021-01-27 15:17 ` rguenther at suse dot de
2021-01-27 16:33 ` cvs-commit at gcc dot gnu.org
2021-01-27 16:34 ` 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-98854-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).