From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
David Hildenbrand <david@redhat.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 2/2] tests/tcg/s390x: Add rxsbg.c
Date: Wed, 15 Mar 2023 19:30:01 +0100 [thread overview]
Message-ID: <1b4f2d623ec943e280fa1c3b6343edf960bb41e1.camel@linux.ibm.com> (raw)
In-Reply-To: <70ded204-a499-0c23-6949-42244fc5bfe9@redhat.com>
On Wed, 2023-03-15 at 19:12 +0100, Thomas Huth wrote:
> On 15/03/2023 00.34, Ilya Leoshkevich wrote:
> > Add a small test for RXSBG with T=1 to prevent regressions.
> >
> > Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
> > ---
> > tests/tcg/s390x/Makefile.target | 1 +
> > tests/tcg/s390x/rxsbg.c | 25 +++++++++++++++++++++++++
> > 2 files changed, 26 insertions(+)
> > create mode 100644 tests/tcg/s390x/rxsbg.c
> >
> > diff --git a/tests/tcg/s390x/Makefile.target
> > b/tests/tcg/s390x/Makefile.target
> > index cf93b966862..b4d0d704534 100644
> > --- a/tests/tcg/s390x/Makefile.target
> > +++ b/tests/tcg/s390x/Makefile.target
> > @@ -29,6 +29,7 @@ TESTS+=clst
> > TESTS+=long-double
> > TESTS+=cdsg
> > TESTS+=chrl
> > +TESTS+=rxsbg
> >
> > cdsg: CFLAGS+=-pthread
> > cdsg: LDFLAGS+=-pthread
> > diff --git a/tests/tcg/s390x/rxsbg.c b/tests/tcg/s390x/rxsbg.c
> > new file mode 100644
> > index 00000000000..b7f35411899
> > --- /dev/null
> > +++ b/tests/tcg/s390x/rxsbg.c
> > @@ -0,0 +1,25 @@
> > +/*
> > + * Smoke test RXSBG instruction with T=1.
> > + * SPDX-License-Identifier: GPL-2.0-or-later
> > + */
> > +#include <assert.h>
> > +#include <stdlib.h>
> > +
> > +int main(void)
> > +{
> > + unsigned long r1, r2, cc;
> > +
> > + r1 = 0xc8dc86a225a77bb4;
> > + r2 = 0xd6aff24fa3e7320;
> > + cc = 0;
> > + asm("rxsbg %[r1],%[r2],177,43,228\n"
> > + "ipm %[cc]"
> > + : [cc] "+r" (cc)
> > + : [r1] "r" (r1)
> > + , [r2] "r" (r2)
> > + : "cc");
> > + cc = (cc >> 28) & 1;
> > + assert(cc == 1);
> > +
> > + return EXIT_SUCCESS;
> > +}
>
> This also fails with Clang 15:
> tests/tcg/s390x/rxsbg.c:15:9: error: invalid operand for instruction
> asm("rxsbg %[r1],%[r2],177,43,228\n"
> ^
> <inline asm>:1:23: note: instantiated into assembly here
> rxsbg %r1,%r2,177,43,228
> ^
>
> Thomas
>
This seems to be a clang bug. PoP says:
Bit 1 of the I3 field and bits 0-1 of the I4 field (bits 17
and 24-25 of the instruction) are reserved and should
contain zeros; otherwise, the program may not oper-
ate compatibly in the future. Bits 0-1 of the I5 field
(bits 32-33 of the instruction) are ignored.
But LLVM has:
imm32zx8:$I4, imm32zx6:$I5
which looks like a mixup (should be imm32zx6 + imm32zx8 IMHO).
I guess there is not much we can do about this at the moment, so I will
choose another constant for the test and send a v2.
prev parent reply other threads:[~2023-03-15 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 23:34 [PATCH 0/2] target/s390x: Fix R[NOX]SBG with T=1 Ilya Leoshkevich
2023-03-14 23:34 ` [PATCH 1/2] " Ilya Leoshkevich
2023-03-15 8:59 ` David Hildenbrand
2023-03-14 23:34 ` [PATCH 2/2] tests/tcg/s390x: Add rxsbg.c Ilya Leoshkevich
2023-03-15 18:12 ` Thomas Huth
2023-03-15 18:30 ` Ilya Leoshkevich [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=1b4f2d623ec943e280fa1c3b6343edf960bb41e1.camel@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=david@redhat.com \
--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).