From: Peter Maydell <peter.maydell@linaro.org>
To: Vacha Bhavsar <vacha.bhavsar@oss.qualcomm.com>
Cc: qemu-devel@nongnu.org, qemu-arm@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Huth" <thuth@redhat.com>
Subject: Re: [PATCH v5 4/4] target/arm: Added test case for SME register exposure
Date: Sat, 23 Aug 2025 19:13:17 +0100 [thread overview]
Message-ID: <CAFEAcA9Bf7kWL20hzCQP5GSAN1AkX0FnqZv_TdTOpQFLSTCdeA@mail.gmail.com> (raw)
In-Reply-To: <CAEWVDmsqgrnXgte0Sb+uzHmu=jHkXWvfHhYme-9hwng3XvrwVA@mail.gmail.com>
On Fri, 22 Aug 2025 at 18:32, Vacha Bhavsar
<vacha.bhavsar@oss.qualcomm.com> wrote:
>
> Hi,
>
> We have tried to replicate this issue on our end and it
> seems to stem from the int casting of gdb.Value type of
> a 128bit integer. We have run the test with different
> host architectures, gdb versions and python versions
> both with and without the int casting. The results are
> as follows.
>
> gdb gdb target python host int cast status
> version support version architecture
> 16.3 --enable-targets=all 3.11.13 x86 yes pass
> 16.3 --enable-targets=all 3.11.13 x86 no pass
> 16.3 --enable-targets=all 3.10.18 x86 yes pass
> 16.3 --enable-targets=all 3.10.18 x86 no pass
> 16.3 --enable-targets=all 3.8.10 x86 yes pass
> 16.3 --enable-targets=all 3.8.10 x86 no pass
>
> 16.3 aarch64 3.11.0rc1 aarch64 yes pass
> 16.3 aarch64 3.11.0rc1 aarch64 no pass
> 16.3 aarch64 3.10.12 aarch64 yes pass
> 16.3 aarch64 3.10.12 aarch64 no pass
>
> 15.0 multiarch 3.10.12 aarch64 yes fail
> 15.0 multiarch 3.10.12 aarch64 no pass
> 15.0 multiarch 3.11.0rc1 aarch64 yes fail
> 15.0 multiarch 3.11.0rc1 aarch64 no pass
>
> 15.0 multiarch 3.8.10 x86 yes fail
> 15.0 multiarch 3.8.10 x86 no pass
> 15.0 multiarch 3.11.13 x86 yes fail
> 15.0 multiarch 3.11.13 x86 no pass
> 15.0 multiarch 3.10.18 x86 yes fail
> 15.0 multiarch 3.10.18 x86 no pass
>
> Could we get some more information about your testing environment?
It's just stock Ubuntu 24.04.3 LTS on x86-64; gdb is gdb-multiarch
GNU gdb (Ubuntu 15.0.50.20240403-0ubuntu1) 15.0.50.20240403-git
-- PMM
next prev parent reply other threads:[~2025-08-23 18:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 19:36 [PATCH v5 0/4] target/arm: Added support for SME register exposure to GDB Vacha Bhavsar
2025-08-11 19:36 ` [PATCH v5 1/4] target/arm: Increase MAX_PACKET_LENGTH for SME ZA Vacha Bhavsar
2025-08-19 9:14 ` Peter Maydell
2025-08-11 19:36 ` [PATCH v5 2/4] target/arm: Change GDBState's line_buf to a GString Vacha Bhavsar
2025-08-12 11:32 ` Peter Maydell
2025-08-12 19:31 ` Vacha Bhavsar
2025-08-11 19:36 ` [PATCH v5 3/4] target/arm: Added support for SME register exposure to Vacha Bhavsar
2025-08-19 9:04 ` Peter Maydell
2025-08-21 21:37 ` Vacha Bhavsar
2025-08-22 12:27 ` Peter Maydell
2025-08-26 18:52 ` Vacha Bhavsar
2025-08-11 19:36 ` [PATCH v5 4/4] target/arm: Added test case for SME register exposure Vacha Bhavsar
2025-08-19 9:13 ` Peter Maydell
2025-08-22 17:32 ` Vacha Bhavsar
2025-08-23 18:13 ` Peter Maydell [this message]
2025-08-26 18:51 ` Vacha Bhavsar
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=CAFEAcA9Bf7kWL20hzCQP5GSAN1AkX0FnqZv_TdTOpQFLSTCdeA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=vacha.bhavsar@oss.qualcomm.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).