From: Richard Henderson <richard.henderson@linaro.org>
To: Khem Raj <raj.khem@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] linux-user: Replace __u64 with uint64_t
Date: Wed, 10 Nov 2021 10:25:20 +0100 [thread overview]
Message-ID: <0242a761-cd00-1a22-e64c-952befad9988@linaro.org> (raw)
In-Reply-To: <20211108194230.1836262-1-raj.khem@gmail.com>
On 11/8/21 8:42 PM, Khem Raj wrote:
> uint64_t is available in all userspaces via compiler include stdint.h
> therefore use it instead of __u64 which is linux internal type, it fixes
> build on some platforms eg. aarch64 systems using musl C library
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> linux-user/host/aarch64/hostdep.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/linux-user/host/aarch64/hostdep.h b/linux-user/host/aarch64/hostdep.h
> index a8d41a21ad..34d934f665 100644
> --- a/linux-user/host/aarch64/hostdep.h
> +++ b/linux-user/host/aarch64/hostdep.h
> @@ -25,7 +25,7 @@ extern char safe_syscall_end[];
> static inline void rewind_if_in_safe_syscall(void *puc)
> {
> ucontext_t *uc = puc;
> - __u64 *pcreg = &uc->uc_mcontext.pc;
> + uint64_t *pcreg = &uc->uc_mcontext.pc;
>
> if (*pcreg > (uintptr_t)safe_syscall_start
> && *pcreg < (uintptr_t)safe_syscall_end) {
Queued to tcg-next, since that's where the original patch came from.
r~
next prev parent reply other threads:[~2021-11-10 9:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 19:42 [PATCH] linux-user: Replace __u64 with uint64_t Khem Raj
2021-11-09 9:09 ` Philippe Mathieu-Daudé
2021-11-09 16:39 ` Warner Losh
2021-11-10 9:25 ` Richard Henderson [this message]
2021-11-10 15:12 ` Richard Henderson
2021-11-10 15:18 ` Richard Henderson
2021-11-10 16:03 ` Warner Losh
2021-11-10 16:31 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2021-11-08 19:51 Khem Raj
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=0242a761-cd00-1a22-e64c-952befad9988@linaro.org \
--to=richard.henderson@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=raj.khem@gmail.com \
/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).