From: Alan Modra <amodra@gmail.com>
To: binutils@sourceware.org
Subject: Error compiling libctf-regression test
Date: Sat, 20 Apr 2024 11:13:19 +0930 [thread overview]
Message-ID: <ZiMdt2rCPKXYd78R@squeak.grove.modra.org> (raw)
Seen on 64-bit targets.
ERROR: compilation of lookup program .../libctf-regression/gzrewrite.c failed
* testsuite/libctf-regression/gzrewrite.c (main): Use %zu to
print size_t values.
* testsuite/libctf-regression/zrewrite.c (main): Likewise.
diff --git a/libctf/testsuite/libctf-regression/gzrewrite.c b/libctf/testsuite/libctf-regression/gzrewrite.c
index 8e279ca3fac..99722200950 100644
--- a/libctf/testsuite/libctf-regression/gzrewrite.c
+++ b/libctf/testsuite/libctf-regression/gzrewrite.c
@@ -88,7 +88,7 @@ main (int argc, char *argv[])
if (a_len != b_len || memcmp (a, b, a_len) != 0)
{
- fprintf (stderr, "consecutive gzwrites are different: lengths %i and %i\n", a_len, b_len);
+ fprintf (stderr, "consecutive gzwrites are different: lengths %zu and %zu\n", a_len, b_len);
return 1;
}
diff --git a/libctf/testsuite/libctf-regression/zrewrite.c b/libctf/testsuite/libctf-regression/zrewrite.c
index 4d5d15e7985..a88c824b568 100644
--- a/libctf/testsuite/libctf-regression/zrewrite.c
+++ b/libctf/testsuite/libctf-regression/zrewrite.c
@@ -83,7 +83,7 @@ main (int argc, char *argv[])
if (a_len != b_len || memcmp (a, b, a_len) != 0)
{
- fprintf (stderr, "consecutive compress_writes are different: lengths %i and %i\n", a_len, b_len);
+ fprintf (stderr, "consecutive compress_writes are different: lengths %zu and %zu\n", a_len, b_len);
return 1;
}
--
Alan Modra
Australia Development Lab, IBM
next reply other threads:[~2024-04-20 1:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 1:43 Alan Modra [this message]
2024-04-20 10:51 ` Nick Alcock
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=ZiMdt2rCPKXYd78R@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).