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/98868] New: [8/9/10/11 Regression] polyhedron rnflow.f90 regression since r8-2555-g344be1fd47d7d64e
Date: Thu, 28 Jan 2021 15:26:57 +0000	[thread overview]
Message-ID: <bug-98868-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 98868
           Summary: [8/9/10/11 Regression] polyhedron rnflow.f90
                    regression since r8-2555-g344be1fd47d7d64e
           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
  Target Milestone: ---

Since the revision the benchmark is much slower:

$ gfortran rnflow.f90 -Ofast -march=znver1 && time ./a.out >/dev/null

0m7.690s -> 0m13.121s

One can see it here:
https://lnt.opensuse.org/db_default/v4/CPP/graph?plot.0=194.791.0&plot.1=188.791.0&plot.2=202.791.0&plot.3=154.791.0&plot.4=245.791.0&plot.5=171.791.0&

             reply	other threads:[~2021-01-28 15:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28 15:26 marxin at gcc dot gnu.org [this message]
2021-01-29  7:43 ` [Bug tree-optimization/98868] " rguenth at gcc dot gnu.org
2021-01-29  8:24 ` rguenth at gcc dot gnu.org
2021-01-29  9:09 ` marxin at gcc dot gnu.org
2021-01-29  9:21 ` rguenther at suse dot de
2021-01-29  9:22 ` marxin at gcc dot gnu.org
2021-01-29  9:36 ` rguenth at gcc dot gnu.org
2021-01-29  9:38 ` 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-98868-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).