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/107021] New: [13 Regression] 511.povray_r error with -Ofast -march=znver2 -flto since r13-2810-gb7fd7fb5011106
Date: Fri, 23 Sep 2022 20:14:35 +0000	[thread overview]
Message-ID: <bug-107021-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107021
           Summary: [13 Regression] 511.povray_r error with -Ofast
                    -march=znver2 -flto since r13-2810-gb7fd7fb5011106
           Product: gcc
           Version: 13.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: aldyh at gcc dot gnu.org
            Blocks: 26163
  Target Milestone: ---

Since the revision, the benchmark is likely miscompiled.

Running Benchmarks
  Running 511.povray_r test peak gcc-m64 (1 copy) [2022-09-23 22:12:20]
511.povray_r: copy 0 non-zero return code (exit code=1, signal=0)


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
[Bug 26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)

             reply	other threads:[~2022-09-23 20:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 20:14 marxin at gcc dot gnu.org [this message]
2022-09-23 20:17 ` [Bug tree-optimization/107021] " marxin at gcc dot gnu.org
2022-09-23 20:24 ` pinskia at gcc dot gnu.org
2022-09-26  9:17 ` rguenth at gcc dot gnu.org
2022-09-26  9:54 ` marxin at gcc dot gnu.org
2022-09-26 10:05 ` marxin at gcc dot gnu.org
2022-09-26 10:45 ` rguenth at gcc dot gnu.org
2022-09-26 10:52 ` marxin at gcc dot gnu.org
2022-09-26 10:53 ` rguenth at gcc dot gnu.org
2022-09-30 14:35 ` pinskia at gcc dot gnu.org
2022-10-18  8:41 ` rguenth at gcc dot gnu.org
2024-05-02 21:11 ` jamborm 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-107021-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).