From: Thomas Huth <thuth@redhat.com>
To: "Richard Henderson" <richard.henderson@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org
Cc: "open list:S390 TCG CPUs" <qemu-s390x@nongnu.org>,
Cornelia Huck <cohuck@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
David Hildenbrand <david@redhat.com>
Subject: Re: [RFC PATCH] tests/tcg: drop -cpu max from s390x sha512-mvx invocation
Date: Thu, 10 Mar 2022 13:28:19 +0100 [thread overview]
Message-ID: <647e89a6-07f5-128b-71fb-9473d28fc69d@redhat.com> (raw)
In-Reply-To: <f036a033-fca7-0125-b90c-0e840d79a59e@linaro.org>
On 10/03/2022 12.35, Richard Henderson wrote:
> On 3/10/22 02:21, Thomas Huth wrote:
>> On 10/03/2022 09.36, Thomas Huth wrote:
[...]
>>> However, the error still persists. I now had a closer look by running the
>>> test with "qemu-s390x" on my z15 machine directly, and all tests are
>>> failing! The problem happens with both, gcc v11.2.1 and clang v13.0.1.
>>> The problem goes away (i.e. test works fine) if I compile the code with
>>> -O1 instead of -O3, or if I use GCC v8.5 instead. I'll try to find out
>>> more, but as a temporary workaround, we could also switch to -O1 instead
>>> of -O3.
>>
>> I noticed that the problem does not occur when running the test natively
>> on my s390x box, or via qemu-s390x on my x86 laptop, or when running it
>> via qemu-s390x v6.1.0 on my s390x box. So it's something wrong in the TCG
>> backend, I think, and I was able to bisect the issue down to this commit
>> here:
>>
>> $ git bisect bad
>> 9bca986df88b8ea46b100e3d21cc9e653c83e0b3 is the first bad commit
>> commit 9bca986df88b8ea46b100e3d21cc9e653c83e0b3
>> Author: Richard Henderson <richard.henderson@linaro.org>
>> Date: Mon Sep 14 20:36:36 2020 -0700
>>
>> tcg/s390x: Implement TCG_TARGET_HAS_bitsel_vec
>>
>> Richard, could you please have a look?
[...]> Ok, will look soon.
> Would you pop this into an issue so I don't forget, please?
Sure, I've created a ticket here:
https://gitlab.com/qemu-project/qemu/-/issues/898
Thomas
next prev parent reply other threads:[~2022-03-10 12:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 11:22 [RFC PATCH] tests/tcg: drop -cpu max from s390x sha512-mvx invocation Alex Bennée
2022-03-09 11:23 ` David Hildenbrand
2022-03-09 20:44 ` Richard Henderson
2022-03-10 8:36 ` Thomas Huth
2022-03-10 10:21 ` Thomas Huth
2022-03-10 11:35 ` Richard Henderson
2022-03-10 12:28 ` Thomas Huth [this message]
2022-03-10 10:34 ` Alex Bennée
2022-03-10 10:41 ` Thomas Huth
2022-03-10 11:33 ` Alex Bennée
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=647e89a6-07f5-128b-71fb-9473d28fc69d@redhat.com \
--to=thuth@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@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).