From: Bastian Koppelmann <kbastian@mail.uni-paderborn.de>
To: qemu-devel@nongnu.org
Cc: rth@twiddle.net
Subject: [Qemu-devel] [PATCH 0/8] TriCore add instructions of RR and RR1 opcode format
Date: Fri, 12 Dec 2014 17:31:36 +0000 [thread overview]
Message-ID: <1418405504-11175-1-git-send-email-kbastian@mail.uni-paderborn.de> (raw)
Hi,
here is the next patchset for the TriCore ISA, which steadily moves towards being a usable qemu guest.
This patchset first cleans up the SSOV/SUOV makros, which were only suitable for 32 bit arithmetic,
to make room for 16bit SSOV/SUOV arithmetic used for the RR insn. These are splitted into four patches,
seperated by the first opcode all insn of one patch have. I also added missed 1.6 insns and fixed some
minor errors. The last patch adds the first half of the RR1 insn.
Cheers,
Bastian
Bastian Koppelmann (8):
target-tricore: Change SSOV/SUOV makro name to SSOV32/SUOV32
target-tricore: Add instructions of RR opcode format, that have 0xb as
the first opcode
target-tricore: Add instructions of RR opcode format, that have 0xf as
the first opcode
target-tricore: Add instructions of RR opcode format, that have 0x1 as
the first opcode
target-tricore: Add instructions of RR opcode format, that have 0x4b
as the first opcode
target-tricore: Add missing 1.6 insn of BOL opcode format
target-tricore: Fix MFCR/MTCR insn and B format offset.
target-tricore: Add instructions of RR1 opcode format, that have 0xb3
as first opcode
target-tricore/helper.h | 68 +++
target-tricore/op_helper.c | 1033 +++++++++++++++++++++++++++++++++++++-
target-tricore/translate.c | 900 ++++++++++++++++++++++++++++++++-
target-tricore/tricore-opcodes.h | 14 +-
4 files changed, 1992 insertions(+), 23 deletions(-)
--
2.1.3
next reply other threads:[~2014-12-12 16:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 17:31 Bastian Koppelmann [this message]
2014-12-12 17:31 ` [Qemu-devel] [PATCH 1/8] target-tricore: Change SSOV/SUOV makro name to SSOV32/SUOV32 Bastian Koppelmann
2014-12-12 19:31 ` Richard Henderson
2014-12-12 17:31 ` [Qemu-devel] [PATCH 2/8] target-tricore: Add instructions of RR opcode format, that have 0xb as the first opcode Bastian Koppelmann
2014-12-12 19:49 ` Richard Henderson
2014-12-12 17:31 ` [Qemu-devel] [PATCH 3/8] target-tricore: Add instructions of RR opcode format, that have 0xf " Bastian Koppelmann
2014-12-12 20:04 ` Richard Henderson
2014-12-12 17:31 ` [Qemu-devel] [PATCH 4/8] target-tricore: Add instructions of RR opcode format, that have 0x1 " Bastian Koppelmann
2014-12-12 20:06 ` Richard Henderson
2014-12-12 17:31 ` [Qemu-devel] [PATCH 5/8] target-tricore: Add instructions of RR opcode format, that have 0x4b " Bastian Koppelmann
2014-12-12 20:45 ` Richard Henderson
2014-12-17 15:43 ` Bastian Koppelmann
2014-12-12 17:31 ` [Qemu-devel] [PATCH 6/8] target-tricore: Add missing 1.6 insn of BOL opcode format Bastian Koppelmann
2014-12-12 20:46 ` Richard Henderson
2014-12-12 17:31 ` [Qemu-devel] [PATCH 7/8] target-tricore: Fix MFCR/MTCR insn and B format offset Bastian Koppelmann
2014-12-12 20:49 ` Richard Henderson
2014-12-12 17:31 ` [Qemu-devel] [PATCH 8/8] target-tricore: Add instructions of RR1 opcode format, that have 0xb3 as first opcode Bastian Koppelmann
2014-12-12 20:53 ` Richard Henderson
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=1418405504-11175-1-git-send-email-kbastian@mail.uni-paderborn.de \
--to=kbastian@mail.uni-paderborn.de \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).