From: Nicholas Krause <xerofoify@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] Use proper print formatter in main function in fixincl.c
Date: Thu, 20 Dec 2018 22:27:00 -0000 [thread overview]
Message-ID: <20181220222353.16951-1-xerofoify@gmail.com> (raw)
This fixes the bug id, 71176 to use the proper known
code print formatter type, %lu for size_t rather than
%d which is considered best pratice for print statements.
Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
---
fixincludes/fixincl.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fixincludes/fixincl.c b/fixincludes/fixincl.c
index 6dba2f6e830..5b8b77a77f0 100644
--- a/fixincludes/fixincl.c
+++ b/fixincludes/fixincl.c
@@ -158,11 +158,11 @@ main (int argc, char** argv)
if (VLEVEL( VERB_PROGRESS )) {
tSCC zFmt[] =
"\
-Processed %5d files containing %d bytes \n\
+Processed %5d files containing %lu bytes \n\
Applying %5d fixes to %d files\n\
Altering %5d of them\n";
- fprintf (stderr, zFmt, process_ct, ttl_data_size, apply_ct,
+ fprintf (stderr, zFmt, process_ct, (unsigned int long) ttl_data_size, apply_ct,
fixed_ct, altered_ct);
}
#endif /* DO_STATS */
--
2.17.1
next reply other threads:[~2018-12-20 22:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-20 22:27 Nicholas Krause [this message]
2019-01-07 15:57 ` Jonathan Wakely
2019-01-07 16:02 ` NightStrike
2019-01-07 16:04 ` Jonathan Wakely
-- strict thread matches above, loose matches on Subject: below --
2018-12-20 2:49 Nicholas Krause
2018-12-20 21:07 ` Joseph Myers
2018-12-20 22:19 ` nick
2018-12-19 23:35 Nicholas Krause
2018-12-20 0:20 ` Joseph Myers
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=20181220222353.16951-1-xerofoify@gmail.com \
--to=xerofoify@gmail.com \
--cc=gcc-patches@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: 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).