From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Akihiko Odaki <akihiko.odaki@daynix.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 3/6] tests/tcg/aarch64: Explicitly specify register width
Date: Wed, 26 Jun 2024 13:59:47 +0200 [thread overview]
Message-ID: <6be35719-6dc0-4e3a-b0db-3614f0c028b0@linaro.org> (raw)
In-Reply-To: <20240626-tcg-v1-3-0bad656307d8@daynix.com>
On 26/6/24 13:26, Akihiko Odaki wrote:
> clang version 18.1.6 assumes a register is 64-bit by default and
> complains if a 32-bit value is given. Explicitly specify register width
> when passing a 32-bit value.
>
> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> ---
> tests/tcg/aarch64/bti-1.c | 6 +++---
> tests/tcg/aarch64/bti-3.c | 6 +++---
> 2 files changed, 6 insertions(+), 6 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
next prev parent reply other threads:[~2024-06-26 12:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 11:26 [PATCH 0/6] tests/tcg/aarch64: Fix inline assemblies for clang Akihiko Odaki
2024-06-26 11:26 ` [PATCH 1/6] tests/tcg/arm: Fix fcvt result messages Akihiko Odaki
2024-06-26 11:26 ` [PATCH 2/6] tests/tcg/aarch64: Fix test architecture specification Akihiko Odaki
2024-06-26 16:12 ` Alex Bennée
2024-06-26 16:15 ` Alex Bennée
2024-06-26 11:26 ` [PATCH 3/6] tests/tcg/aarch64: Explicitly specify register width Akihiko Odaki
2024-06-26 11:59 ` Philippe Mathieu-Daudé [this message]
2024-06-26 11:26 ` [PATCH 4/6] tests/tcg/aarch64: Fix irg operand type Akihiko Odaki
2024-06-26 11:26 ` [PATCH 5/6] tests/tcg/aarch64: Do not use x constraint Akihiko Odaki
2024-06-26 11:26 ` [PATCH 6/6] tests/tcg/arm: Manually bit-cast half-precision numbers Akihiko Odaki
2024-06-26 14:09 ` [PATCH 0/6] tests/tcg/aarch64: Fix inline assemblies for clang Alex Bennée
2024-06-27 13:28 ` Akihiko Odaki
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=6be35719-6dc0-4e3a-b0db-3614f0c028b0@linaro.org \
--to=philmd@linaro.org \
--cc=akihiko.odaki@daynix.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).