From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH] http: fix some printf format warnings on 32-bit builds
Date: Wed, 11 Nov 2015 20:58:24 +0000 [thread overview]
Message-ID: <5643ABF0.5080207@ramsayjones.plus.com> (raw)
In-Reply-To: <CAPig+cS54yTsZ8NWjyh6kj6nXy966EkYPHh_sjMbMcDGemnFuA@mail.gmail.com>
On 11/11/15 20:31, Eric Sunshine wrote:
> On Wed, Nov 11, 2015 at 12:47 PM, Ramsay Jones
> <ramsay@ramsayjones.plus.com> wrote:
>> On 11/11/15 01:22, Eric Sunshine wrote:
>>> On Tue, Nov 10, 2015 at 7:23 PM, Ramsay Jones
>>> <ramsay@ramsayjones.plus.com> wrote:
>>> My machine is 64-bit, though, so perhaps it's misleading to
>>> characterize this as a fix for 32-bit builds. In particular, off_t is
>>> 'long long' on this machine, so it complains about the "long" format
>>> specifier.
>>
>> ... but this seems to imply that sizeof(long) is 4 on your machine, right?
>> (on x86_64 linux it's 8, which is why I hadn't noticed before).
>
> This code on my Mac:
>
> printf("sizeof(long)=%zu\n", sizeof(long));
> printf("sizeof(long long)=%zu\n", sizeof(long long));
> printf("sizeof(off_t)=%zu\n", sizeof(off_t));
>
> produces:
>
> sizeof(long)=8
> sizeof(long long)=8
> sizeof(off_t)=8
>
> The fact that 'long' and 'long long' happen to be the same size (in
> this case) is immaterial. What is important is that the code is just
> wrong to be using the "%l" specifier for 'long' when the actual
> datatype is 'long long' (which is what 'off_t' is under-the-hood in
> this case).
Ah. OK, so %ld for long and %lld for long long, I suppose.
Hmm, not that it matters, but I wonder what the PRId64 macro is. ;-)
ATB,
Ramsay Jones
next prev parent reply other threads:[~2015-11-11 20:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 0:23 [PATCH] http: fix some printf format warnings on 32-bit builds Ramsay Jones
2015-11-11 1:22 ` Eric Sunshine
2015-11-11 2:00 ` Stefan Beller
2015-11-11 8:02 ` Lars Schneider
2015-11-11 17:38 ` Stefan Beller
2015-11-11 17:49 ` Ramsay Jones
2015-11-13 8:46 ` Lars Schneider
2015-11-13 8:57 ` Eric Sunshine
2015-11-13 10:32 ` Torsten Bögershausen
2015-11-13 12:08 ` Lars Schneider
2015-11-13 20:02 ` Ramsay Jones
2015-11-14 19:14 ` Lars Schneider
2015-11-11 17:47 ` Ramsay Jones
2015-11-11 20:31 ` Eric Sunshine
2015-11-11 20:54 ` Jeff King
2015-11-11 20:58 ` Ramsay Jones [this message]
2015-11-12 5:27 ` Torsten Bögershausen
2015-11-12 11:58 ` Ramsay Jones
2015-11-12 18:40 ` Andreas Schwab
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=5643ABF0.5080207@ramsayjones.plus.com \
--to=ramsay@ramsayjones.plus.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=sunshine@sunshineco.com \
/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).