public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-4504] testsuite: Use -mnofpu for rx-*-* in ieee testsuite [PR107046] Date: Tue, 6 Dec 2022 10:43:41 +0000 (GMT) [thread overview] Message-ID: <20221206104341.576E73850B37@sourceware.org> (raw) 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. Diff: --- gcc/testsuite/gcc.c-torture/execute/ieee/ieee.exp | 3 +++ 1 file changed, 3 insertions(+) diff --git a/gcc/testsuite/gcc.c-torture/execute/ieee/ieee.exp b/gcc/testsuite/gcc.c-torture/execute/ieee/ieee.exp index 6d3c371d6ef..fda34a7f935 100644 --- a/gcc/testsuite/gcc.c-torture/execute/ieee/ieee.exp +++ b/gcc/testsuite/gcc.c-torture/execute/ieee/ieee.exp @@ -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"
reply other threads:[~2022-12-06 10:43 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221206104341.576E73850B37@sourceware.org \ --to=jakub@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).