From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, alex.bennee@linaro.org
Subject: Re: [PATCH v3 0/2] accel/tcg: Improvements to atomic128.h
Date: Thu, 25 May 2023 17:24:52 -0700 [thread overview]
Message-ID: <a18c646e-f2cf-b4f8-4f23-cb73e44ea38e@linaro.org> (raw)
In-Reply-To: <20230524183258.1194571-1-richard.henderson@linaro.org>
On 5/24/23 11:32, Richard Henderson wrote:
> Changes for v3:
> * Most of the v2 patch set merged, except x86_64 atomic128-ldst.h,
> which failed testing with clang-11 with debian 11.
>
> * New patch to change __int128_t detection.
>
> * This in turn enabled CONFIG_ATOMIC128, which was not ideal.
> This clang bug/mis-feature of using a cmpxchg sequence for
> implementing __atomic_load_n was already noted for aarch64,
> so I should have expected it would also be true for x86_64.
> Given that I am adding inline assembly for CPUINFO_ATOMIC_VMOVDQA
> anyway, this isn't a big deal, but I did need to adjust the ifdefs.
>
>
> r~
>
>
> Richard Henderson (2):
> meson: Split test for __int128_t type from __int128_t arithmetic
> qemu/atomic128: Add x86_64 atomic128-ldst.h
>
> meson.build | 15 +++--
> host/include/x86_64/host/atomic128-ldst.h | 68 +++++++++++++++++++++++
> include/qemu/int128.h | 4 +-
> 3 files changed, 80 insertions(+), 7 deletions(-)
> create mode 100644 host/include/x86_64/host/atomic128-ldst.h
>
Superseded by
Message-Id: <20230526002334.1760495-1-richard.henderson@linaro.org>
r~
prev parent reply other threads:[~2023-05-26 0:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 18:32 [PATCH v3 0/2] accel/tcg: Improvements to atomic128.h Richard Henderson
2023-05-24 18:32 ` [PATCH v3 1/2] meson: Split test for __int128_t type from __int128_t arithmetic Richard Henderson
2023-05-24 18:32 ` [PATCH v3 2/2] qemu/atomic128: Add x86_64 atomic128-ldst.h Richard Henderson
2023-05-26 0:24 ` Richard Henderson [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=a18c646e-f2cf-b4f8-4f23-cb73e44ea38e@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=peter.maydell@linaro.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).