From: Florian Achleitner <florian.achleitner.2.6.31@gmail.com>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: florian.achleitner.2.6.31@gmail.com,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH] fast_export.c: Fix a compiler warning
Date: Mon, 20 Aug 2012 08:19:25 +0200 [thread overview]
Message-ID: <2715225.vOk3BtNY6o@flomedio> (raw)
In-Reply-To: <5031063E.3090405@ramsay1.demon.co.uk>
On Sunday 19 August 2012 16:29:02 Ramsay Jones wrote:
> In particular, gcc complains thus:
>
> CC vcs-svn/fast_export.o
> vcs-svn/fast_export.c: In function 'fast_export_begin_note':
> vcs-svn/fast_export.c:77: warning: long long unsigned int format, \
> different type arg (arg 2)
>
> In order to fix the warning, we cast the second size_t argument in
> the call to printf to uintmax_t.
>
> Signed-off-by: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
> ---
>
> Hi Florian,
>
> If you need to re-roll your patches in the 'fa/remote-svn' branch, could
> you please squash this fix into them. [This was implemented on top of
> commit 2ce959ba, but you will probably want to make the equivalent change
> to commit d319a37c ("Create a note for every imported commit containing
> svn metadata", 17-08-2012) instead. Note that, because of the context
> lines in the patch, it won't apply as-is.]
Ok, I'll add it to the next version. This warning only occurs when building
for 32bit, thus I never saw it. There would be a format flag for printf that
sprecifies the platform's size_t integer type: "z".
Probalby we should use it instead? I don't know how widely supported it is.
>
> Thanks!
>
> ATB,
> Ramsay Jones
Thanks,
Florian
>
> vcs-svn/fast_export.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/vcs-svn/fast_export.c b/vcs-svn/fast_export.c
> index c780d32..dd09c7d 100644
> --- a/vcs-svn/fast_export.c
> +++ b/vcs-svn/fast_export.c
> @@ -74,7 +74,7 @@ void fast_export_begin_note(uint32_t revision, const char
> *author, size_t loglen = strlen(log);
> printf("commit %s\n", note_ref);
> printf("committer %s <%s@%s> %ld +0000\n", author, author, "local",
> timestamp); - printf("data %"PRIuMAX"\n", loglen);
> + printf("data %"PRIuMAX"\n", (uintmax_t) loglen);
> fwrite(log, loglen, 1, stdout);
> if (firstnote) {
> if (revision > 1)
next prev parent reply other threads:[~2012-08-20 6:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-19 15:29 [PATCH] fast_export.c: Fix a compiler warning Ramsay Jones
2012-08-20 6:19 ` Florian Achleitner [this message]
2012-08-20 6:50 ` Junio C Hamano
2012-08-21 18:58 ` Ramsay Jones
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=2715225.vOk3BtNY6o@flomedio \
--to=florian.achleitner.2.6.31@gmail.com \
--cc=git@vger.kernel.org \
--cc=ramsay@ramsay1.demon.co.uk \
/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