From: Max Filippov <jcmvbkbc@gmail.com>
To: qemu-devel@nongnu.org
Cc: Richard Henderson <richard.henderson@linaro.org>,
Max Filippov <jcmvbkbc@gmail.com>
Subject: [Qemu-devel] [PATCH 0/3] target/xtensa: add basic FLIX support
Date: Wed, 30 Jan 2019 15:54:39 -0800 [thread overview]
Message-ID: <20190130235442.2876-1-jcmvbkbc@gmail.com> (raw)
Hello,
this series adds limited support for FLIX instructions.
FLIX (flexible length instruction extensions) allows bundling multiple
opcodes in a single instruction. Each opcode is executed as if it was
the only opcode in the instruction. Opcodes may not simultaneously
modify same resource (register or state). Multiple branches, even
non-taken, are also not allowed in one instruction.
Instructions with opcodes that have circular dependencies between used
resources (e.g. opcode A uses resource U and modifies resource M, while
opcode B uses resource M and modifies resource U) are not supported in
this series.
Max Filippov (3):
target/xtensa: sort FLIX instruction opcodes
target/xtensa: add generic instruction post-processing
target/xtensa: move WINDOW_BASE SR update to postprocessing
target/xtensa/cpu.h | 5 +
target/xtensa/helper.h | 3 +-
target/xtensa/translate.c | 265 +++++++++++++++++++++++++++++++++++++++++----
target/xtensa/win_helper.c | 14 +--
4 files changed, 251 insertions(+), 36 deletions(-)
--
2.11.0
next reply other threads:[~2019-01-30 23:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 23:54 Max Filippov [this message]
2019-01-30 23:54 ` [Qemu-devel] [PATCH 1/3] target/xtensa: sort FLIX instruction opcodes Max Filippov
2019-01-30 23:54 ` [Qemu-devel] [PATCH 2/3] target/xtensa: add generic instruction post-processing Max Filippov
2019-01-30 23:54 ` [Qemu-devel] [PATCH 3/3] target/xtensa: move WINDOW_BASE SR update to postprocessing Max Filippov
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=20190130235442.2876-1-jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).