From: Thomas Huth <thuth@redhat.com>
To: Cao Jiaxi <driver1998@foxmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 3/4] util/cacheinfo.c: Use uintptr_t instead of unsigned long in AArch64 arch_cache_info()
Date: Thu, 2 May 2019 10:26:31 +0200 [thread overview]
Message-ID: <6e3335b8-a5ce-ef0a-bf24-08165d877a2a@redhat.com> (raw)
In-Reply-To: <20190430181326.1314-1-driver1998@foxmail.com>
On 30/04/2019 20.13, Cao Jiaxi wrote:
> Windows ARM64 uses LLP64 model, which breaks current assumptions.
>
> Signed-off-by: Cao Jiaxi <driver1998@foxmail.com>
> ---
> util/cacheinfo.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/util/cacheinfo.c b/util/cacheinfo.c
> index 3cd080b83d..ce6f0dbf6a 100644
> --- a/util/cacheinfo.c
> +++ b/util/cacheinfo.c
> @@ -107,7 +107,7 @@ static void sys_cache_info(int *isize, int *dsize)
> static void arch_cache_info(int *isize, int *dsize)
> {
> if (*isize == 0 || *dsize == 0) {
> - unsigned long ctr;
> + uintptr_t ctr;
Looking at the whole function, is uintptr_t really the right type to use
here? ctr does not seem to contain the value of a pointer variable, so
this looks wrong to me...
Do you get a compiler warning here? If so, how does it look like?
Anyway, I think it would be better to use a uint64_t or uint32_t type
here instead if possible?
Thomas
next prev parent reply other threads:[~2019-05-02 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 18:13 [Qemu-devel] [PATCH v2 3/4] util/cacheinfo.c: Use uintptr_t instead of unsigned long in AArch64 arch_cache_info() Cao Jiaxi
2019-04-30 18:13 ` Cao Jiaxi
2019-04-30 19:12 ` Philippe Mathieu-Daudé
2019-04-30 19:12 ` Philippe Mathieu-Daudé
2019-05-01 15:35 ` Philippe Mathieu-Daudé
2019-05-01 15:35 ` Philippe Mathieu-Daudé
2019-05-02 8:26 ` Thomas Huth [this message]
2019-05-02 8:26 ` Thomas Huth
2019-05-02 16:31 ` Richard Henderson
2019-05-02 16:31 ` Richard Henderson
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=6e3335b8-a5ce-ef0a-bf24-08165d877a2a@redhat.com \
--to=thuth@redhat.com \
--cc=driver1998@foxmail.com \
--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).