Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: John Baldwin <jhb@FreeBSD.org>
To: gdb-patches@sourceware.org
Subject: [PATCH 4/5] sim mn10300: Fix igen generation.
Date: Wed, 14 Apr 2021 16:02:58 -0700	[thread overview]
Message-ID: <20210414230259.19234-5-jhb@FreeBSD.org> (raw)
In-Reply-To: <20210414230259.19234-1-jhb@FreeBSD.org>

Only pass the top-level instruction decode table (mn10300.igen) to
igen via -i.  The additional files passed previously caused igen to
exit its getopt loop in main and exit silently without generating any
output.  In addition, when am33-2.igen was added, it was not included
from mn10300.igen, so was never used.

sim/mn10300/ChangeLog:

	* Makefile.in: (tmp-igen) Only pass mn10300.igen to igen.
	* mn10300.igen: Include am33-2.igen.
---
 sim/mn10300/ChangeLog    | 5 +++++
 sim/mn10300/Makefile.in  | 5 +++--
 sim/mn10300/mn10300.igen | 1 +
 3 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/sim/mn10300/ChangeLog b/sim/mn10300/ChangeLog
index 5638b8621ef..ad1eb66df0b 100644
--- a/sim/mn10300/ChangeLog
+++ b/sim/mn10300/ChangeLog
@@ -1,3 +1,8 @@
+2021-04-14  John Baldwin  <jhb@FreeBSD.org>
+
+	* Makefile.in: (tmp-igen) Only pass mn10300.igen to igen.
+	* mn10300.igen: Include am33-2.igen.
+
 2021-04-12  Mike Frysinger  <vapier@gentoo.org>
 
 	* interp.c (sim_open): Delete 3rd arg to sim_cpu_alloc_all.
diff --git a/sim/mn10300/Makefile.in b/sim/mn10300/Makefile.in
index 773b7f9a0c5..120958fce6d 100644
--- a/sim/mn10300/Makefile.in
+++ b/sim/mn10300/Makefile.in
@@ -66,9 +66,10 @@ clean-igen:
 	rm -f tmp-igen tmp-insns
 
 IGEN_TRACE= # -G omit-line-numbers # -G trace-rule-selection -G trace-rule-rejection -G trace-entries
-IGEN_INSN=$(srcdir)/mn10300.igen $(srcdir)/am33.igen $(srcdir)/am33-2.igen
+IGEN_INSN=$(srcdir)/mn10300.igen
+IGEN_INSN_INC=$(srcdir)/am33.igen $(srcdir)/am33-2.igen
 IGEN_DC=$(srcdir)/mn10300.dc
-tmp-igen: $(IGEN_INSN) $(IGEN_DC) ../igen/igen
+tmp-igen: $(IGEN_INSN) $(IGEN_INSN_INC) $(IGEN_DC) ../igen/igen
 	$(IGEN) \
 		$(IGEN_TRACE) \
 		-G gen-direct-access \
diff --git a/sim/mn10300/mn10300.igen b/sim/mn10300/mn10300.igen
index c7b83ed141f..80a394309c9 100644
--- a/sim/mn10300/mn10300.igen
+++ b/sim/mn10300/mn10300.igen
@@ -4590,4 +4590,5 @@
 
 
 :include::am33:am33.igen
+:include::am33-2:am33-2.igen
 
-- 
2.30.1


  parent reply	other threads:[~2021-04-14 23:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14 23:02 [PATCH 0/5] Various build fixes for sims John Baldwin
2021-04-14 23:02 ` [PATCH 1/5] sim: Add SIM_EXTRA_CFLAGS after CSEARCH John Baldwin
2021-04-14 23:56   ` Mike Frysinger via Gdb-patches
2021-04-14 23:02 ` [PATCH 2/5] sim frv: Add a missing return value for frvbf_check_acc_range John Baldwin
2021-04-14 23:54   ` Mike Frysinger via Gdb-patches
2021-11-10  9:33   ` Mike Frysinger via Gdb-patches
2021-04-14 23:02 ` [PATCH 3/5] sim lm32: Use a known-good shell with genmloop.sh John Baldwin
2021-04-14 23:55   ` Mike Frysinger via Gdb-patches
2021-04-14 23:02 ` John Baldwin [this message]
2021-04-14 23:53   ` [PATCH 4/5] sim mn10300: Fix igen generation Mike Frysinger via Gdb-patches
2021-04-14 23:02 ` [PATCH 5/5] sim erc32: Add include path for readline John Baldwin
2021-04-14 23:56   ` Mike Frysinger via Gdb-patches

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=20210414230259.19234-5-jhb@FreeBSD.org \
    --to=jhb@freebsd.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