From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH] sim: mips: simplify fpu configure logic
Date: Fri, 4 Nov 2022 01:38:26 +0700 [thread overview]
Message-ID: <20221103183826.23637-1-vapier@gentoo.org> (raw)
The configure code always defaults to HARD_FLOATING_POINT, so inline
that value and drop redundant target checks as a result.
---
sim/mips/configure | 18 +++++++-----------
sim/mips/configure.ac | 18 +++++++-----------
2 files changed, 14 insertions(+), 22 deletions(-)
diff --git a/sim/mips/configure.ac b/sim/mips/configure.ac
index bdc675842d38..f1d9f3d24100 100644
--- a/sim/mips/configure.ac
+++ b/sim/mips/configure.ac
@@ -45,20 +45,16 @@ SIM_AC_OPTION_BITSIZE($mips_bitsize,$mips_msb)
#
# Select the floating hardware support of the target
#
-mips_fpu=HARDWARE_FLOATING_POINT
mips_fpu_bitsize=
case "${target}" in
- mips*tx39*) mips_fpu=HARD_FLOATING_POINT ; mips_fpu_bitsize=32 ;;
- mips*-sde-elf*) mips_fpu=HARD_FLOATING_POINT ; mips_fpu_bitsize=64 ;;
- mips*-mti-elf*) mips_fpu=HARD_FLOATING_POINT ; mips_fpu_bitsize=64 ;;
- mips64*-*-*) mips_fpu=HARD_FLOATING_POINT ;;
- mips16*-*-*) mips_fpu=HARD_FLOATING_POINT ;;
- mipsisa32*-*-*) mips_fpu=HARD_FLOATING_POINT ; mips_fpu_bitsize=64 ;;
- mipsisa64*-*-*) mips_fpu=HARD_FLOATING_POINT ; mips_fpu_bitsize=64 ;;
- mips*-*-*) mips_fpu=HARD_FLOATING_POINT ; mips_fpu_bitsize=32 ;;
- *) mips_fpu=HARD_FLOATING_POINT ;;
+ mips*tx39*) mips_fpu_bitsize=32 ;;
+ mips*-sde-elf*) mips_fpu_bitsize=64 ;;
+ mips*-mti-elf*) mips_fpu_bitsize=64 ;;
+ mipsisa32*-*-*) mips_fpu_bitsize=64 ;;
+ mipsisa64*-*-*) mips_fpu_bitsize=64 ;;
+ mips*-*-*) mips_fpu_bitsize=32 ;;
esac
-SIM_AC_OPTION_FLOAT($mips_fpu,$mips_fpu_bitsize)
+SIM_AC_OPTION_FLOAT(HARD_FLOATING_POINT,$mips_fpu_bitsize)
--
2.38.1
next reply other threads:[~2022-11-03 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 18:38 Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-03 18:37 Mike Frysinger
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=20221103183826.23637-1-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.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).