public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Petter Tomner <tomner@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-5559] jit: Change printf specifiers for size_t to %zu Date: Sat, 27 Nov 2021 15:53:33 +0000 (GMT) [thread overview] Message-ID: <20211127155333.53C7F3858C3A@sourceware.org> (raw) https://gcc.gnu.org/g:1e53408452448cdfa5481e25e470946c2c472539 commit r12-5559-g1e53408452448cdfa5481e25e470946c2c472539 Author: Petter Tomner <tomner@kth.se> Date: Sat Nov 27 15:52:15 2021 +0100 jit: Change printf specifiers for size_t to %zu Change four occurances of %ld specifier for size_t to %zu for clean 32bit builds. Signed-off-by 2021-11-27 Petter Tomner <tomner@kth.se> gcc/jit/ * libgccjit.c: %ld -> %zu Diff: --- gcc/jit/libgccjit.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/jit/libgccjit.c b/gcc/jit/libgccjit.c index c744b634f4b..5d051e43e1e 100644 --- a/gcc/jit/libgccjit.c +++ b/gcc/jit/libgccjit.c @@ -707,7 +707,7 @@ gcc_jit_function_type_get_param_type (gcc_jit_function_type *function_type, gcc::jit::recording::context *ctxt = function_type->m_ctxt; RETURN_NULL_IF_FAIL_PRINTF3 (index < num_params, ctxt, NULL, - "index of %ld is too large (%s has %ld params)", + "index of %zu is too large (%s has %zu params)", index, function_type->get_debug_string (), num_params); @@ -951,7 +951,7 @@ gcc_jit_struct_get_field (gcc_jit_struct *struct_type, size_t num_fields = struct_type->get_fields ()->length (); RETURN_NULL_IF_FAIL_PRINTF3 (index < num_fields, NULL, NULL, - "index of %ld is too large (%s has %ld fields)", + "index of %zu is too large (%s has %zu fields)", index, struct_type->get_debug_string (), num_fields);
reply other threads:[~2021-11-27 15:53 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211127155333.53C7F3858C3A@sourceware.org \ --to=tomner@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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: linkBe 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).