public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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: Tue, 06 Dec 2022 10:43:42 +0000	[thread overview]
Message-ID: <bug-107046-4-9zNV8MWTLp@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 #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:8872df353884fec6d7ff0e8bf8eee356439ec8d8

commit r13-4504-g8872df353884fec6d7ff0e8bf8eee356439ec8d8
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Tue Dec 6 11:39:51 2022 +0100

    testsuite: Use -mnofpu for rx-*-* in ieee testsuite [PR107046]

    add_options_for_ieee has:
        if { [istarget alpha*-*-*]
             || [istarget sh*-*-*] } {
           return "$flags -mieee"
        }
        if { [istarget rx-*-*] } {
           return "$flags -mnofpu"
        }
    but ieee.exp doesn't use add_options_for_ieee, instead it has:
    if { [istarget "alpha*-*-*"]
         || [istarget "sh*-*-*"] } then {
      lappend additional_flags "-mieee"
    }
    among other things (plus -ffloat-store on some arches etc.).

    The following patch adds the rx -mnofpu similarly in the hope
    of fixing ieee.exp FAILs on rx.

    Preapproved in the PR by Jeff, committed to trunk.

    2022-12-06  Jakub Jelinek  <jakub@redhat.com>

            PR testsuite/107046
            * gcc.c-torture/execute/ieee/ieee.exp: For rx-*-* append
            -mnofpu.

  parent reply	other threads:[~2022-12-06 10:43 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
2022-12-05 18:47 ` law at gcc dot gnu.org
2022-12-06 10:43 ` cvs-commit at gcc dot gnu.org [this message]
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-9zNV8MWTLp@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).