From: Akihiko Odaki <akihiko.odaki@daynix.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/6] tests/tcg/aarch64: Fix inline assemblies for clang
Date: Thu, 27 Jun 2024 22:28:01 +0900 [thread overview]
Message-ID: <d30df7ac-62c7-44cd-ba88-a7f757f034d8@daynix.com> (raw)
In-Reply-To: <878qyrpzgw.fsf@draig.linaro.org>
On 2024/06/26 23:09, Alex Bennée wrote:
> Akihiko Odaki <akihiko.odaki@daynix.com> writes:
>
>> Unlike GCC, clang checks if the operands in assembly matches with the
>> type in C. It also does not support "x" constraint for AArch64 and
>> complains about them.
>
> When are the test cases ever built with clang? Is this for Arm on Arm
> testing only?
I ran test QEMU built with clang on Asahi Linux.
prev parent reply other threads:[~2024-06-27 13:28 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é
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 [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=d30df7ac-62c7-44cd-ba88-a7f757f034d8@daynix.com \
--to=akihiko.odaki@daynix.com \
--cc=alex.bennee@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.