public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jeffreyalaw at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/107046] [13 Regression] Recent FP range work causing inf-2 to be miscompiled on rx-elf
Date: Tue, 27 Sep 2022 20:12:05 +0000 [thread overview]
Message-ID: <bug-107046-4-QXEZRJq0iy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107046-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107046
--- Comment #5 from Jeffrey A. Law <jeffreyalaw at gmail dot com> ---
First, let's not focus too much on that specific test. There's others:
Tests that now fail, but worked before (20 tests):
rx-sim: gcc.c-torture/execute/ieee/hugeval.c execution, -O1
rx-sim: gcc.c-torture/execute/ieee/hugeval.c execution, -O2
rx-sim: gcc.c-torture/execute/ieee/hugeval.c execution, -O2 -flto
-fno-use-linker-plugin -flto-partition=none
rx-sim: gcc.c-torture/execute/ieee/hugeval.c execution, -O2 -flto
-fuse-linker-plugin -fno-fat-lto-objects
rx-sim: gcc.c-torture/execute/ieee/hugeval.c execution, -O3 -g
rx-sim: gcc.c-torture/execute/ieee/hugeval.c execution, -Os
rx-sim: gcc.c-torture/execute/ieee/inf-2.c execution, -O1
rx-sim: gcc.c-torture/execute/ieee/inf-2.c execution, -O2
rx-sim: gcc.c-torture/execute/ieee/inf-2.c execution, -O2 -flto
-fno-use-linker-plugin -flto-partition=none
rx-sim: gcc.c-torture/execute/ieee/inf-2.c execution, -O2 -flto
-fuse-linker-plugin -fno-fat-lto-objects
rx-sim: gcc.c-torture/execute/ieee/inf-2.c execution, -O3 -g
rx-sim: gcc.c-torture/execute/ieee/inf-2.c execution, -Og -g
rx-sim: gcc.c-torture/execute/ieee/inf-2.c execution, -Os
rx-sim: gcc.c-torture/execute/ieee/inf-3.c execution, -O1
rx-sim: gcc.c-torture/execute/ieee/inf-3.c execution, -O2
rx-sim: gcc.c-torture/execute/ieee/inf-3.c execution, -O2 -flto
-fno-use-linker-plugin -flto-partition=none
rx-sim: gcc.c-torture/execute/ieee/inf-3.c execution, -O2 -flto
-fuse-linker-plugin -fno-fat-lto-objects
rx-sim: gcc.c-torture/execute/ieee/inf-3.c execution, -O3 -g
rx-sim: gcc.c-torture/execute/ieee/inf-3.c execution, -Og -g
rx-sim: gcc.c-torture/execute/ieee/inf-3.c execution, -Os
Given the magic hackery going on inside the RX target files, I wonder if we
should skip the entire ieee suite for rx.
next prev parent reply other threads:[~2022-09-27 20:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 23:44 [Bug tree-optimization/107046] New: " jeffreyalaw at gmail dot com
2022-09-27 7:20 ` [Bug tree-optimization/107046] " aldyh at gcc dot gnu.org
2022-09-27 8:54 ` rguenth at gcc dot gnu.org
2022-09-27 8:59 ` rguenth at gcc dot gnu.org
2022-09-27 9:39 ` [Bug testsuite/107046] " aldyh at gcc dot gnu.org
2022-09-27 20:12 ` jeffreyalaw at gmail dot com [this message]
2022-12-02 11:16 ` jakub at gcc dot gnu.org
2022-12-05 18:47 ` law at gcc dot gnu.org
2022-12-06 10:43 ` cvs-commit at gcc dot gnu.org
2022-12-22 14:33 ` rguenth at gcc dot gnu.org
2022-12-22 16:08 ` law 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-107046-4-QXEZRJq0iy@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).