From: Richard Henderson <richard.henderson@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: fam@euphon.net, Peter Maydell <peter.maydell@linaro.org>,
berrange@redhat.com, f4bug@amsat.org, qemu-arm@nongnu.org,
stefanha@redhat.com, crosa@redhat.com, pbonzini@redhat.com,
aurelien@aurel32.net
Subject: Re: [PATCH v1 09/11] tests/tcg: build sha1-vector with O3 and compare
Date: Sat, 12 Feb 2022 08:50:48 +1100 [thread overview]
Message-ID: <1f319e1b-a117-979a-eb5a-09e8aedfaf62@linaro.org> (raw)
In-Reply-To: <20220211160309.335014-10-alex.bennee@linaro.org>
On 2/12/22 03:03, Alex Bennée wrote:
> The aim of this is to test code generation for vectorised operations.
> Unfortunately gcc struggles to do much with the messy sha1 code (try
> -fopt-info-vec-missed to see why). However it's better than nothing.
>
> We assume the non-vectorised output is gold and baring compiler bugs
> the outputs should match.
>
> Signed-off-by: Alex Bennée<alex.bennee@linaro.org>
> Message-Id:<20220202191242.652607-3-alex.bennee@linaro.org>
> ---
> tests/tcg/aarch64/Makefile.target | 10 ++++++++++
> tests/tcg/arm/Makefile.target | 9 +++++++++
> 2 files changed, 19 insertions(+)
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2022-02-11 21:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 16:02 [PATCH v1 00/11] testing/next (docker, lcitool, ci, tcg) Alex Bennée
2022-02-11 16:02 ` [PATCH v1 01/11] tests/docker: restore TESTS/IMAGES filtering Alex Bennée
2022-02-11 16:03 ` [PATCH v1 02/11] tests/docker: add NOUSER for alpine image Alex Bennée
2022-02-11 16:23 ` Daniel P. Berrangé
2022-02-11 17:51 ` Alex Bennée
2022-02-11 18:08 ` Daniel P. Berrangé
2022-02-11 16:03 ` [PATCH v1 03/11] tests/lcitool: update to latest version Alex Bennée
2022-02-11 16:03 ` [PATCH v1 04/11] tests/docker: update debian-arm64-cross with lci-tool Alex Bennée
2022-02-11 21:08 ` Richard Henderson
2022-02-11 16:03 ` [PATCH v1 05/11] tests/docker: introduce debian-riscv64-test-cross Alex Bennée
2022-02-11 21:09 ` Richard Henderson
2022-02-11 16:03 ` [PATCH v1 06/11] scripts/ci: add build env rules for aarch32 on aarch64 Alex Bennée
2022-02-11 16:03 ` [PATCH v1 07/11] scripts/ci: allow for a secondary runner Alex Bennée
2022-02-11 16:03 ` [PATCH v1 08/11] gitlab: add a new aarch32 custom runner definition Alex Bennée
2022-02-11 16:03 ` [PATCH v1 09/11] tests/tcg: build sha1-vector with O3 and compare Alex Bennée
2022-02-11 21:50 ` Richard Henderson [this message]
2022-02-11 16:03 ` [PATCH v1 10/11] tests/tcg: add sha512 test Alex Bennée
2022-02-11 16:03 ` [PATCH v1 11/11] tests/tcg: add vectorised sha512 versions Alex Bennée
2022-02-14 14:17 ` Matheus K. Ferst
2022-02-14 15:14 ` Alex Bennée
2022-02-17 12:46 ` Matheus K. Ferst
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=1f319e1b-a117-979a-eb5a-09e8aedfaf62@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=aurelien@aurel32.net \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).