From: Peter Maydell <peter.maydell@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org
Subject: Re: [RFC PATCH] include/exec: fix softmmu version of TARGET_ABI_FMT_lx
Date: Tue, 8 Feb 2022 15:51:41 +0000 [thread overview]
Message-ID: <CAFEAcA-UX4h-vCvQtkyZ803H+HyL_-o+dFgR54BUEAkFSEAoQw@mail.gmail.com> (raw)
In-Reply-To: <20220208125909.3031809-1-alex.bennee@linaro.org>
On Tue, 8 Feb 2022 at 15:42, Alex Bennée <alex.bennee@linaro.org> wrote:
>
> TARGET_ABI_FMT_lx isn't available for softmmu which causes confusion
> when trying to print. As abi_ptr == target_ulong use its format string
> instead.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> include/exec/cpu_ldst.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/exec/cpu_ldst.h b/include/exec/cpu_ldst.h
> index a878fd0105..da987fe8ad 100644
> --- a/include/exec/cpu_ldst.h
> +++ b/include/exec/cpu_ldst.h
> @@ -121,7 +121,7 @@ static inline bool guest_range_valid_untagged(abi_ulong start, abi_ulong len)
> })
> #else
> typedef target_ulong abi_ptr;
> -#define TARGET_ABI_FMT_ptr TARGET_ABI_FMT_lx
> +#define TARGET_ABI_FMT_ptr TARGET_FMT_lx
> #endif
>
> uint32_t cpu_ldub_data(CPUArchState *env, abi_ptr ptr);
I think this was clearly just a bug that we never noticed because
we haven't tried using TARGET_ABI_FMT_ptr in softmmu code before.
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
I do still wonder whether the softmmu code in question really
ought to be using abi_ptr, though.
thanks
-- PMM
prev parent reply other threads:[~2022-02-08 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 12:59 [RFC PATCH] include/exec: fix softmmu version of TARGET_ABI_FMT_lx Alex Bennée
2022-02-08 15:51 ` Peter Maydell [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=CAFEAcA-UX4h-vCvQtkyZ803H+HyL_-o+dFgR54BUEAkFSEAoQw@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@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).