qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: peter.maydell@linaro.org
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org,
	richard.henderson@linaro.org,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: [Qemu-devel] [PATCH REPOST v1 0/8] Group support and random clean-ups
Date: Fri, 23 Feb 2018 15:46:05 +0000	[thread overview]
Message-ID: <20180223154613.2096-1-alex.bennee@linaro.org> (raw)

Hi,

This is essentially a re-post but with a wider distribution. There is
one extra patch which adds the FP16 1 source data processing. This is for
discussion on how best to represent all the different architectural
versions by using the second field in the aarch64.risu file.

Alex Bennée (8):
  risugen: support @GroupName in risu files
  aarch64.risu: clean-up and annotate with groups
  aarch64.risu: add cryptographic extensions for v8.2
  new contrib/generate_all.sh: batch risugen script
  contrib/run_risu.sh: allow appending of QEMU_FLAGS
  contrib/run_risu.sh: don't set -e
  contrib/run_risu.sh: add a visual cue for a clean-run
  aarch64.risu: update Floating-point data-processing (1 source)

 README                  |  10 ++
 aarch64.risu            | 287 +++++++++++++++++++++++++++++++++---------------
 contrib/generate_all.sh |  96 ++++++++++++++++
 contrib/run_risu.sh     |  10 +-
 risugen                 |  24 +++-
 5 files changed, 335 insertions(+), 92 deletions(-)
 create mode 100755 contrib/generate_all.sh

-- 
2.15.1

             reply	other threads:[~2018-02-23 15:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-23 15:46 Alex Bennée [this message]
2018-02-23 15:46 ` [Qemu-devel] [PATCH v1 1/8] risugen: support @GroupName in risu files Alex Bennée
2018-02-23 15:46 ` [Qemu-devel] [PATCH v1 2/8] aarch64.risu: clean-up and annotate with groups Alex Bennée
2018-02-23 15:46 ` [Qemu-devel] [PATCH v1 3/8] aarch64.risu: add cryptographic extensions for v8.2 Alex Bennée
2018-02-23 18:17   ` Peter Maydell
2018-02-23 15:46 ` [Qemu-devel] [PATCH v1 4/8] new contrib/generate_all.sh: batch risugen script Alex Bennée
2018-02-23 16:17   ` Daniel P. Berrangé
2018-02-23 16:42     ` Peter Maydell
2018-02-23 16:45     ` Alex Bennée
2018-02-23 16:49       ` Daniel P. Berrangé
2018-02-23 17:01         ` Peter Maydell
2018-02-23 17:05           ` Daniel P. Berrangé
2018-02-23 15:46 ` [Qemu-devel] [PATCH v1 5/8] contrib/run_risu.sh: allow appending of QEMU_FLAGS Alex Bennée
2018-02-23 18:12   ` Peter Maydell
2018-02-23 15:46 ` [Qemu-devel] [PATCH v1 6/8] contrib/run_risu.sh: don't set -e Alex Bennée
2018-02-23 15:46 ` [Qemu-devel] [PATCH v1 7/8] contrib/run_risu.sh: add a visual cue for a clean-run Alex Bennée
2018-02-23 15:46 ` [Qemu-devel] [PATCH v1 8/8] aarch64.risu: update Floating-point data-processing (1 source) Alex Bennée
2018-02-23 18:23 ` [Qemu-devel] [PATCH REPOST v1 0/8] Group support and random clean-ups Peter Maydell
2018-03-01 11: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=20180223154613.2096-1-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --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).