From: Jose Ricardo Ziviani <joserz@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [Qemu-devel] [PATCH Risu v2 3/9] Change mode directive of ARM risu files
Date: Sun, 6 Nov 2016 15:15:22 -0200 [thread overview]
Message-ID: <1478452528-13684-4-git-send-email-joserz@linux.vnet.ibm.com> (raw)
In-Reply-To: <1478452528-13684-1-git-send-email-joserz@linux.vnet.ibm.com>
If different risufiles are managed by a single risugen (like
thumb.risu, aarch64.risu, and arm.risu are managed by
risugen_arm.pm) the mode directive identifies such operation
by prepending the module name:
thumb.risu - .mode arm.thumb
aarch64.risu = .mode arm.aarch64
arm.risu = .mode arm
Signed-off-by: Jose Ricardo Ziviani <joserz@linux.vnet.ibm.com>
---
aarch64.risu | 2 +-
arm.risu | 1 +
thumb.risu | 2 +-
3 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/aarch64.risu b/aarch64.risu
index 6957f95..2f3341c 100644
--- a/aarch64.risu
+++ b/aarch64.risu
@@ -11,7 +11,7 @@
###############################################################################
# Input file for risugen defining AArch64 instructions
-.mode aarch64
+.mode arm.aarch64
# from ARM DDI 0487A.a ARM Architecture Reference Manual
# XXX NIY: branch, exception generation, system insns
diff --git a/arm.risu b/arm.risu
index 025a87b..13ea019 100644
--- a/arm.risu
+++ b/arm.risu
@@ -10,6 +10,7 @@
###############################################################################
# Input file for risugen defining ARM instructions
+.mode arm
# Some random patterns
#ADD A1 cond:4 0000 100 s rn:4 rd:4 imm:5 type:2 0 rm:4
diff --git a/thumb.risu b/thumb.risu
index 8e14c95..bf7556b 100644
--- a/thumb.risu
+++ b/thumb.risu
@@ -11,7 +11,7 @@
# Input file for risugen defining Thumb instructions
-.mode thumb
+.mode arm.thumb
#ADD T1 000 1100 rm:3 rn:3 rd:3
#ADD T3 11101 01 1000 s rn:4 0 imma:3 rd:4 immb:2 type:2 rm:4
--
2.7.4
next prev parent reply other threads:[~2016-11-06 17:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 17:15 [Qemu-devel] [PATCH Risu v2 0/9] Risu support for PPC64LE Jose Ricardo Ziviani
2016-11-06 17:15 ` [Qemu-devel] [PATCH Risu v2 1/9] Create risugen_arm.pm module for risugen Jose Ricardo Ziviani
2016-11-06 17:15 ` [Qemu-devel] [PATCH Risu v2 2/9] Refactor risugen to remove ARM specific code Jose Ricardo Ziviani
2016-11-06 17:15 ` Jose Ricardo Ziviani [this message]
2016-11-06 17:15 ` [Qemu-devel] [PATCH Risu v2 4/9] Implement lib to deal with PPC64 registers Jose Ricardo Ziviani
2017-02-15 18:50 ` Peter Maydell
2017-02-15 19:28 ` joserz
2016-11-06 17:15 ` [Qemu-devel] [PATCH Risu v2 5/9] Implement basic test code for PPC64 Jose Ricardo Ziviani
2016-11-06 17:15 ` [Qemu-devel] [PATCH Risu v2 6/9] Implement initial support " Jose Ricardo Ziviani
2016-11-06 17:15 ` [Qemu-devel] [PATCH Risu v2 7/9] Add PPC64 in risu build system Jose Ricardo Ziviani
2017-02-18 22:41 ` Peter Maydell
2017-02-21 2:24 ` joserz
2017-02-21 9:59 ` Peter Maydell
2016-11-06 17:15 ` [Qemu-devel] [PATCH Risu v2 8/9] Implement risugen module for PPC64 Jose Ricardo Ziviani
2016-11-06 17:15 ` [Qemu-devel] [PATCH Risu v2 9/9] Implement risufile with all PPC64 instructions Jose Ricardo Ziviani
2016-11-07 16:43 ` [Qemu-devel] [PATCH Risu v2 0/9] Risu support for PPC64LE Peter Maydell
2016-11-07 20:18 ` joserz
2016-11-07 20:44 ` Peter Maydell
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=1478452528-13684-4-git-send-email-joserz@linux.vnet.ibm.com \
--to=joserz@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).