public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/107098] New: [13 regression] failure in 453.povray
Date: Fri, 30 Sep 2022 14:32:23 +0000	[thread overview]
Message-ID: <bug-107098-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107098
           Summary: [13 regression] failure in 453.povray
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: seurer at gcc dot gnu.org
  Target Milestone: ---

Now at commit g:b7fd7fb5011106c062df9275ca8fddcbce4ebdeb, r13-2810 

commit b7fd7fb5011106c062df9275ca8fddcbce4ebdeb
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Thu Sep 22 18:20:39 2022 +0200

    frange: drop endpoints to min/max representable numbers for
-ffinite-math-only.


This commit breaks one of the spec2006 test cases on powerpc64 LE

Running Benchmarks
  Running 453.povray ref base ppc64 default
453.povray: copy 0 non-zero return code (exit code=127, signal=0)
Invalid run; unable to continue.

Note that -ffinite-math-only is not used in compiling the source.  Sample
compilation:

/home/seurer/gcc/git/install/gcc-test/bin/g++ -c -o bcyl.o -DSPEC_CPU -DNDEBUG 
 -m64 -O3 -mcpu=power8 -ffast-math -funroll-loops -fpeel-loops
-fvect-cost-model -mpopcntd -mrecip=rsqrt           bcyl.cpp

Or is that option included by one of the others?

I am not seeing anything in the log of the run that indicates what the error
was unfortunately.

             reply	other threads:[~2022-09-30 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 14:32 seurer at gcc dot gnu.org [this message]
2022-09-30 14:34 ` [Bug other/107098] [13 regression] failure in 453.povray after r13-2810-gb7fd7fb5011106 seurer at gcc dot gnu.org
2022-09-30 14:35 ` 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-107098-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).