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] [13 Regression] 511.povray_r error with -Ofast -march=znver2 -flto since r13-2810-gb7fd7fb5011106
Date: Mon, 26 Sep 2022 09:54:04 +0000 [thread overview]
Message-ID: <bug-107021-4-gVqP3mEkeH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107021-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107021
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2022-09-26
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Yep, it exits here:
#0 __GI_exit (status=1) at exit.c:142
#1 0x00000000002b0961 in povray_exit (i=1) at
/home/marxin/Programming/cpu2017/benchspec/CPU/511.povray_r/build/build_peak_gcc-m64.0002/povray.cpp:486
#2 0x00000000002e3ede in pov::Error (format=<optimized out>) at
/home/marxin/Programming/cpu2017/benchspec/CPU/511.povray_r/build/build_peak_gcc-m64.0002/userio.cpp:365
#3 0x0000000000270f16 in pov::Parse_Camera (Camera_Ptr=<optimized out>) at
/home/marxin/Programming/cpu2017/benchspec/CPU/511.povray_r/build/build_peak_gcc-m64.0002/parse.cpp:1423
#4 0x000000000028083f in pov::Parse_Frame () at
/home/marxin/Programming/cpu2017/benchspec/CPU/511.povray_r/build/build_peak_gcc-m64.0002/parse.cpp:6125
#5 0x00000000002c0557 in pov::Parse () at
/home/marxin/Programming/cpu2017/benchspec/CPU/511.povray_r/build/build_peak_gcc-m64.0002/parse.cpp:289
parse.cpp contains:
where New->Angle is infinite as assigned here:
1180 New->Angle = HUGE_VAL;
#if __GNUC_PREREQ (3, 3)
# define HUGE_VAL (__builtin_huge_val ())
#else
next prev parent reply other threads:[~2022-09-26 9:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 20:14 [Bug tree-optimization/107021] New: " marxin at gcc dot gnu.org
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 [this message]
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-gVqP3mEkeH@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).