qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Richard Henderson <richard.henderson@linaro.org>,
	Thomas Huth <thuth@redhat.com>,
	qemu-devel@nongnu.org
Cc: David Hildenbrand <david@redhat.com>
Subject: Re: [PULL 13/21] tests/tcg/s390x: Test MVCRL with a large value in R0
Date: Mon, 10 Jul 2023 15:13:50 +0200	[thread overview]
Message-ID: <c9ea1e35ca0b172db14a2b8cd743a823c540a59d.camel@linux.ibm.com> (raw)
In-Reply-To: <f697c822-8036-d185-cf79-8f71e4dbdee0@linaro.org>

On Mon, 2023-07-10 at 14:09 +0100, Richard Henderson wrote:
> On 7/10/23 13:15, Thomas Huth wrote:
> > From: Ilya Leoshkevich <iii@linux.ibm.com>
> > 
> > Add a small test to prevent regressions.
> > 
> > Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
> > Reviewed-by: David Hildenbrand <david@redhat.com>
> > Message-Id: <20230704081506.276055-13-iii@linux.ibm.com>
> > Signed-off-by: Thomas Huth <thuth@redhat.com>
> > ---
> >   tests/tcg/s390x/mie3-mvcrl.c | 46 ++++++++++++++++++++++++++++---
> > -----
> >   1 file changed, 36 insertions(+), 10 deletions(-)
> > 
> > diff --git a/tests/tcg/s390x/mie3-mvcrl.c b/tests/tcg/s390x/mie3-
> > mvcrl.c
> > index 93c7b0a290..ec78dd1d49 100644
> > --- a/tests/tcg/s390x/mie3-mvcrl.c
> > +++ b/tests/tcg/s390x/mie3-mvcrl.c
> > @@ -1,29 +1,55 @@
> > +#include <stdbool.h>
> >   #include <stdint.h>
> > +#include <stdlib.h>
> >   #include <string.h>
> >   
> > -
> > -static inline void mvcrl_8(const char *dst, const char *src)
> > +static void mvcrl(const char *dst, const char *src, size_t len)
> >   {
> > +    register long r0 asm("r0") = len;
> > +
> >       asm volatile (
> > -        "llill %%r0, 8\n"
> >           ".insn sse, 0xE50A00000000, 0(%[dst]), 0(%[src])"
> > -        : : [dst] "d" (dst), [src] "d" (src)
> > -        : "r0", "memory");
> > +        : : [dst] "d" (dst), [src] "d" (src), "r" (r0)
> > +        : "memory");
> >   }
> >   
> > -
> > -int main(int argc, char *argv[])
> > +static bool test(void)
> >   {
> >       const char *alpha = "abcdefghijklmnop";
> >   
> >       /* array missing 'i' */
> > -    char tstr[17] = "abcdefghjklmnop\0" ;
> > +    char tstr[17] = "abcdefghjklmnop\0";
> >   
> >       /* mvcrl reference use: 'open a hole in an array' */
> > -    mvcrl_8(tstr + 9, tstr + 8);
> > +    mvcrl(tstr + 9, tstr + 8, 8);
> >   
> >       /* place missing 'i' */
> >       tstr[8] = 'i';
> >   
> > -    return strncmp(alpha, tstr, 16ul);
> > +    return strncmp(alpha, tstr, 16ul) == 0;
> > +}
> > +
> > +static bool test_bad_r0(void)
> > +{
> > +    char src[256];
> > +
> > +    /*
> > +     * PoP says: Bits 32-55 of general register 0 should contain
> > zeros;
> > +     * otherwise, the program may not operate compatibly in the
> > future.
> > +     *
> > +     * Try it anyway in order to check whether this would crash
> > QEMU itself.
> > +     */
> > +    mvcrl(src, src, (size_t)-1);
> > +
> > +    return true;
> > +}
> 
> gcc 11 doesn't like this:
> 
> https://gitlab.com/qemu-project/qemu/-/jobs/4623964826#L3921
> 
> /home/gitlab-runner/builds/E8PpwMky/0/qemu-
> project/qemu/tests/tcg/s390x/mie3-mvcrl.c: In 
> function ‘test_bad_r0’:
> /home/gitlab-runner/builds/E8PpwMky/0/qemu-
> project/qemu/tests/tcg/s390x/mie3-mvcrl.c:42:5: 
> error: ‘src’ may be used uninitialized [-Werror=maybe-uninitialized]
>     42 |     mvcrl(src, src, (size_t)-1);
>        |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~
> /home/gitlab-runner/builds/E8PpwMky/0/qemu-
> project/qemu/tests/tcg/s390x/mie3-mvcrl.c:6:13: 
> note: by argument 1 of type ‘const char *’ to ‘mvcrl’ declared here
>      6 | static void mvcrl(const char *dst, const char *src, size_t
> len)
>        |             ^~~~~
> /home/gitlab-runner/builds/E8PpwMky/0/qemu-
> project/qemu/tests/tcg/s390x/mie3-mvcrl.c:34:10: 
> note: ‘src’ declared here
>     34 |     char src[256];
>        |          ^~~
> /home/gitlab-runner/builds/E8PpwMky/0/qemu-
> project/qemu/tests/tcg/s390x/mie3-mvcrl.c:42:5: 
> error: ‘src’ may be used uninitialized [-Werror=maybe-uninitialized]
>     42 |     mvcrl(src, src, (size_t)-1);
>        |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~
> /home/gitlab-runner/builds/E8PpwMky/0/qemu-
> project/qemu/tests/tcg/s390x/mie3-mvcrl.c:6:13: 
> note: by argument 2 of type ‘const char *’ to ‘mvcrl’ declared here
>      6 | static void mvcrl(const char *dst, const char *src, size_t
> len)
>        |             ^~~~~
> /home/gitlab-runner/builds/E8PpwMky/0/qemu-
> project/qemu/tests/tcg/s390x/mie3-mvcrl.c:34:10: 
> note: ‘src’ declared here
>     34 |     char src[256];
>        |          ^~~
> cc1: all warnings being treated as errors
> 
> How it sees any use of the structure, initialized or otherwise, I
> don't know -- it's all 
> hidden within the asm.  However, src[256] = { } is enough to silence
> the error.
> 
> 
> r~

Thanks for having a look at this. I assume you applied this fixup, and
I don't need to send a follow-up patch?


  reply	other threads:[~2023-07-10 13:14 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10 12:15 [PULL 00/21] s390x, qtest and misc patches before the 8.1 soft freeze Thomas Huth
2023-07-10 12:15 ` [PULL 01/21] hw/s390x: Move KVM specific PV from hw/ to target/s390x/kvm/ Thomas Huth
2023-07-10 12:15 ` [PULL 02/21] linux-user: elfload: Add more initial s390x PSW bits Thomas Huth
2023-07-10 12:15 ` [PULL 03/21] target/s390x: Fix EPSW CC reporting Thomas Huth
2023-07-10 12:15 ` [PULL 04/21] target/s390x: Fix MDEB and MDEBR Thomas Huth
2023-07-10 12:15 ` [PULL 05/21] target/s390x: Fix MVCRL with a large value in R0 Thomas Huth
2023-07-10 12:15 ` [PULL 06/21] target/s390x: Fix LRA overwriting the top 32 bits on DAT error Thomas Huth
2023-07-10 12:15 ` [PULL 07/21] target/s390x: Fix LRA when DAT is off Thomas Huth
2023-07-10 12:15 ` [PULL 08/21] target/s390x: Fix relative long instructions with large offsets Thomas Huth
2023-07-10 12:15 ` [PULL 09/21] tests/tcg/s390x: Test EPSW Thomas Huth
2023-07-10 12:15 ` [PULL 10/21] tests/tcg/s390x: Test LARL with a large offset Thomas Huth
2023-07-10 12:15 ` [PULL 11/21] tests/tcg/s390x: Test LRA Thomas Huth
2023-07-10 12:15 ` [PULL 12/21] tests/tcg/s390x: Test MDEB and MDEBR Thomas Huth
2023-07-10 12:15 ` [PULL 13/21] tests/tcg/s390x: Test MVCRL with a large value in R0 Thomas Huth
2023-07-10 13:09   ` Richard Henderson
2023-07-10 13:13     ` Ilya Leoshkevich [this message]
2023-07-10 13:15       ` Thomas Huth
2023-07-10 12:15 ` [PULL 14/21] tests/qtest/readconfig-test: Allow testing for arbitrary memory sizes Thomas Huth
2023-07-10 12:15 ` [PULL 15/21] tests/qtest: Move mkimg() and have_qemu_img() from libqos to libqtest Thomas Huth
2023-07-10 12:15 ` [PULL 16/21] tests/qtest/readconfig: Test the docs/config/q35-*.cfg files Thomas Huth
2023-07-10 12:15 ` [PULL 17/21] os-posix: Allow 'chroot' via '-run-with' and deprecate the old '-chroot' option Thomas Huth
2023-07-10 12:15 ` [PULL 18/21] meson.build: Skip C++ detection unless we're targeting Windows Thomas Huth
2023-07-10 12:15 ` [PULL 19/21] tests/tcg/s390x: Fix test-svc with clang Thomas Huth
2023-07-10 12:15 ` [PULL 20/21] tests/qtest: massively speed up migration-test Thomas Huth
2023-07-10 12:15 ` [PULL 21/21] docs/devel: Fix coding style in style.rst Thomas Huth

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=c9ea1e35ca0b172db14a2b8cd743a823c540a59d.camel@linux.ibm.com \
    --to=iii@linux.ibm.com \
    --cc=david@redhat.com \
    --cc=qemu-devel@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).