From: Paolo Bonzini <pbonzini@redhat.com>
To: "Ilya Leoshkevich" <iii@linux.ibm.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] tests/tcg: Do not use inttypes.h in multiarch/system/memory.c
Date: Thu, 10 Oct 2024 11:20:27 +0200 [thread overview]
Message-ID: <59b7a93e-7acb-4a73-9aae-bbfb36101c5d@redhat.com> (raw)
In-Reply-To: <20241010085906.226249-1-iii@linux.ibm.com>
On 10/10/24 10:58, Ilya Leoshkevich wrote:
> make check-tcg fails on Fedora with the following error message:
>
> alpha-linux-gnu-gcc [...] qemu/tests/tcg/multiarch/system/memory.c -o memory [...]
> qemu/tests/tcg/multiarch/system/memory.c:17:10: fatal error: inttypes.h: No such file or directory
> 17 | #include <inttypes.h>
> | ^~~~~~~~~~~~
> compilation terminated.
>
> The reason is that Fedora has cross-compilers, but no cross-glibc
> headers. Fix by hardcoding the format specifiers and dropping the
> include.
>
> An alternative fix would be to introduce a configure check for
> inttypes.h. But this would make it impossible to use Fedora
> cross-compilers for softmmu tests, which used to work so far.
>
> Fixes: ecbcc9ead2f8 ("tests/tcg: add a system test to check memory instrumentation")
> Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> tests/tcg/multiarch/system/memory.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/tests/tcg/multiarch/system/memory.c b/tests/tcg/multiarch/system/memory.c
> index 65a6038a241..7508f6b916d 100644
> --- a/tests/tcg/multiarch/system/memory.c
> +++ b/tests/tcg/multiarch/system/memory.c
> @@ -14,7 +14,6 @@
>
> #include <stdint.h>
> #include <stdbool.h>
> -#include <inttypes.h>
> #include <minilib.h>
>
> #ifndef CHECK_UNALIGNED
> @@ -511,8 +510,8 @@ int main(void)
> int i;
> bool ok = true;
>
> - ml_printf("Test data start: 0x%"PRIxPTR"\n", &test_data[0]);
> - ml_printf("Test data end: 0x%"PRIxPTR"\n", &test_data[TEST_SIZE]);
> + ml_printf("Test data start: 0x%lx\n", (unsigned long)&test_data[0]);
> + ml_printf("Test data end: 0x%lx\n", (unsigned long)&test_data[TEST_SIZE]);
>
> /* Run through the unsigned tests first */
> for (i = 0; i < ARRAY_SIZE(init_ufns) && ok; i++) {
> @@ -529,8 +528,8 @@ int main(void)
> ok = do_signed_reads(true);
> }
>
> - ml_printf("Test data read: %"PRId32"\n", test_read_count);
> - ml_printf("Test data write: %"PRId32"\n", test_write_count);
> + ml_printf("Test data read: %lu\n", (unsigned long)test_read_count);
> + ml_printf("Test data write: %lu\n", (unsigned long)test_write_count);
> ml_printf("Test complete: %s\n", ok ? "PASSED" : "FAILED");
> return ok ? 0 : -1;
> }
next prev parent reply other threads:[~2024-10-10 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 8:58 [PATCH] tests/tcg: Do not use inttypes.h in multiarch/system/memory.c Ilya Leoshkevich
2024-10-10 9:20 ` Paolo Bonzini [this message]
2024-10-29 23:29 ` Ilya Leoshkevich
2024-11-04 11:34 ` Richard Henderson
2024-12-16 11:26 ` Ilya Leoshkevich
2024-12-16 15:40 ` 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=59b7a93e-7acb-4a73-9aae-bbfb36101c5d@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=iii@linux.ibm.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).