From: Mike Frysinger <vapier@gentoo.org>
To: gdb-patches@sourceware.org
Subject: [PATCH] sim: mips: merge mips64vr4300 with existing multi-run build
Date: Wed, 21 Dec 2022 22:45:38 -0500 [thread overview]
Message-ID: <20221222034538.10335-1-vapier@gentoo.org> (raw)
The existing mips64vr-* multi-run build already handles mips4300
targets, so reuse that for mips64vr43* targets too. This moves
more logic from build-time to runtime so we can have a single
binary that supports many targets.
---
sim/mips/configure | 5 +----
sim/mips/configure.ac | 5 +----
2 files changed, 2 insertions(+), 8 deletions(-)
diff --git a/sim/mips/configure b/sim/mips/configure
index 80963681d4ef..bc762fc04f84 100755
--- a/sim/mips/configure
+++ b/sim/mips/configure
@@ -1847,9 +1847,6 @@ case "${target}" in
sim_igen_filter="32,f"
sim_igen_machine="-M r3900"
;;
- mips64vr43*) sim_gen=IGEN
- sim_igen_machine="-M mipsIV"
- ;;
mips64vr5*) sim_gen=IGEN
sim_igen_machine="-M vr5000"
;;
@@ -1859,7 +1856,7 @@ case "${target}" in
sim_igen_filter="32,64,f"
sim_m16_filter="16"
;;
- mips64vr-* | mips64vrel-*)
+ mips64vr43* | mips64vr-* | mips64vrel-*)
sim_gen=MULTI
sim_multi_configs="\
vr4100:mipsIII,mips16,vr4100:32,64:mips4100,mips4111\
diff --git a/sim/mips/configure.ac b/sim/mips/configure.ac
index bdea84e821cd..a09e9a14c798 100644
--- a/sim/mips/configure.ac
+++ b/sim/mips/configure.ac
@@ -20,9 +20,6 @@ case "${target}" in
sim_igen_filter="32,f"
sim_igen_machine="-M r3900"
;;
- mips64vr43*) sim_gen=IGEN
- sim_igen_machine="-M mipsIV"
- ;;
mips64vr5*) sim_gen=IGEN
sim_igen_machine="-M vr5000"
;;
@@ -32,7 +29,7 @@ case "${target}" in
sim_igen_filter="32,64,f"
sim_m16_filter="16"
;;
- mips64vr-* | mips64vrel-*)
+ mips64vr43* | mips64vr-* | mips64vrel-*)
sim_gen=MULTI
sim_multi_configs="\
vr4100:mipsIII,mips16,vr4100:32,64:mips4100,mips4111\
--
2.39.0
reply other threads:[~2022-12-22 3:45 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=20221222034538.10335-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).