From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>, Ivan Warren <ivan@vmfacility.fr>,
qemu-s390x@nongnu.org,
Richard Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2 0/6] s390x/tcg: Vector instruction fixes
Date: Mon, 21 Oct 2019 18:01:52 +0200 [thread overview]
Message-ID: <20191021180152.78fa879d.cohuck@redhat.com> (raw)
In-Reply-To: <20191021085715.3797-1-david@redhat.com>
On Mon, 21 Oct 2019 10:57:09 +0200
David Hildenbrand <david@redhat.com> wrote:
> Ivan reported that a simple
> $ go get -v -d github.com/FactomProject/factom
>
> Will result in errors when vector instructions are in use. Turns out
> golang makes excessive use of vector instructions, e.g., for crypto, hashes
> but also basic math.
>
> I tracked the involved vector instructions and started writing more
> tests for them (will upstream them once they are in a better shape). Turns
> out there are quite some issues remaining. golang uses instructions not
> yet used by the kernel or by glibc.
>
> With these patches, "go get" works again. It wouldn't surprise me if there
> are more BUGs in the vector instructions. Will continue writing more tests.
>
> Cc: Ivan Warren <ivan@vmfacility.fr>
>
> v1 -> v2:
> - "s390x/tcg: Fix VECTOR SUBTRACT COMPUTE BORROW INDICATION"
> -- Fix by inverting the result
> - "s390x/tcg: Fix VECTOR SUBTRACT WITH BORROW INDICATION"
> -- Reuse gen_ac2_i64()
> - "s390x/tcg: Fix VECTOR SUBTRACT WITH BORROW COMPUTE BORROW INDICATION"
> -- Reuse gen_accc2_i64()
> - Ran against more tests
>
> David Hildenbrand (6):
> s390x/tcg: Fix VECTOR MULTIPLY LOGICAL ODD
> s390x/tcg: Fix VECTOR MULTIPLY AND ADD *
> s390x/tcg: Fix VECTOR SHIFT RIGHT ARITHMETIC BY BYTE
> s390x/tcg: Fix VECTOR SUBTRACT COMPUTE BORROW INDICATION
> s390x/tcg: Fix VECTOR SUBTRACT WITH BORROW INDICATION
> s390x/tcg: Fix VECTOR SUBTRACT WITH BORROW COMPUTE BORROW INDICATION
>
> target/s390x/translate_vx.inc.c | 30 ++++++++++++------------------
> target/s390x/vec_int_helper.c | 18 ++++++++++--------
> 2 files changed, 22 insertions(+), 26 deletions(-)
>
Thanks, applied.
prev parent reply other threads:[~2019-10-21 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 8:57 [PATCH v2 0/6] s390x/tcg: Vector instruction fixes David Hildenbrand
2019-10-21 8:57 ` [PATCH v2 1/6] s390x/tcg: Fix VECTOR MULTIPLY LOGICAL ODD David Hildenbrand
2019-10-21 8:57 ` [PATCH v2 2/6] s390x/tcg: Fix VECTOR MULTIPLY AND ADD * David Hildenbrand
2019-10-21 8:57 ` [PATCH v2 3/6] s390x/tcg: Fix VECTOR SHIFT RIGHT ARITHMETIC BY BYTE David Hildenbrand
2019-10-21 8:57 ` [PATCH v2 4/6] s390x/tcg: Fix VECTOR SUBTRACT COMPUTE BORROW INDICATION David Hildenbrand
2019-10-21 15:23 ` Richard Henderson
2019-10-21 8:57 ` [PATCH v2 5/6] s390x/tcg: Fix VECTOR SUBTRACT WITH " David Hildenbrand
2019-10-21 15:23 ` Richard Henderson
2019-10-21 8:57 ` [PATCH v2 6/6] s390x/tcg: Fix VECTOR SUBTRACT WITH BORROW COMPUTE " David Hildenbrand
2019-10-21 15:24 ` Richard Henderson
2019-10-21 16:01 ` Cornelia Huck [this message]
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=20191021180152.78fa879d.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=ivan@vmfacility.fr \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@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).