public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <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: Fri, 02 Dec 2022 11:16:07 +0000	[thread overview]
Message-ID: <bug-107046-4-NWyYByCXR5@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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Jeffrey A. Law from comment #5)
> Given the magic hackery going on inside the RX target files, I wonder if we
> should skip the entire ieee suite for rx.

Doesn't add_options_for_ieee already handle RX though?
    if { [istarget rx-*-*] } {
       return "$flags -mnofpu"
    }
ieee.exp repeats some of the add_options_for_ieee stuff and more though, so
shouldn't we
--- gcc/testsuite/gcc.c-torture/execute/ieee/ieee.exp.jj        2022-01-11
23:11:22.969282018 +0100
+++ gcc/testsuite/gcc.c-torture/execute/ieee/ieee.exp   2022-12-02
12:15:22.307173074 +0100
@@ -52,6 +52,9 @@ if { [istarget "alpha*-*-*"]
      || [istarget "sh*-*-*"] } then {
   lappend additional_flags "-mieee"
 }
+if [istarget rx-*-*] then {
+  lappend additional_flags "-mnofpu"
+}

 if { ![check_effective_target_signal] } {
     lappend additional_flags "-DSIGNAL_SUPPRESS"
?

  parent reply	other threads:[~2022-12-02 11:16 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
2022-12-02 11:16 ` jakub at gcc dot gnu.org [this message]
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-NWyYByCXR5@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).