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 0/9] Risu support for PPC64LE
Date: Sun, 6 Nov 2016 15:15:19 -0200 [thread overview]
Message-ID: <1478452528-13684-1-git-send-email-joserz@linux.vnet.ibm.com> (raw)
v2:
- smaller commits
- improved registers comparison
- improved code style
- fixed copyright lines
TODOs:
- improve load/store instruction generation (risugen)
- improve initial random values for FP and Vector regs (risugen)
- make write_test_code() generic (risugen)
This is an initial effort to have RISU working for PPC64LE.
I also made some changes to isolate risugen, creating two modules (risugen_arm.pm and risugen_ppc64le.pm) to implement specific instructions in it. Suggestions are welcome! :)
Jose Ricardo Ziviani (9):
Create risugen_arm.pm module for risugen
Refactor risugen to remove ARM specific code
Change mode directive of ARM risu files
Implement lib to deal with PPC64 registers
Implement basic test code for PPC64
Implement initial support for PPC64
Add PPC64 in risu build system
Implement risugen module for PPC64
Implement risufile with all PPC64 instructions
aarch64.risu | 2 +-
arm.risu | 1 +
configure | 8 +-
ppc64.risu | 3448 ++++++++++++++++++++++++++++++++++++++++++++++++
risu_ppc64le.c | 158 +++
risu_reginfo_ppc64le.c | 200 +++
risu_reginfo_ppc64le.h | 40 +
risugen | 1035 +--------------
risugen_arm.pm | 1086 +++++++++++++++
risugen_ppc64.pm | 460 +++++++
test_ppc64le.s | 51 +
thumb.risu | 2 +-
12 files changed, 5478 insertions(+), 1013 deletions(-)
create mode 100644 ppc64.risu
create mode 100644 risu_ppc64le.c
create mode 100644 risu_reginfo_ppc64le.c
create mode 100644 risu_reginfo_ppc64le.h
create mode 100644 risugen_arm.pm
create mode 100644 risugen_ppc64.pm
create mode 100644 test_ppc64le.s
--
2.7.4
next 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 Jose Ricardo Ziviani [this message]
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 ` [Qemu-devel] [PATCH Risu v2 3/9] Change mode directive of ARM risu files Jose Ricardo Ziviani
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-1-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).