size_t/ssize_t warnings (was: Re: Build regressions/improvements in v3.5-rc5)
From: Geert Uytterhoeven
Date: Wed Jul 04 2012 - 16:17:28 EST
On Wed, Jul 4, 2012 at 3:34 PM, Jan Kara <jack@xxxxxxx> wrote:
>> + fs/quota/quota_tree.c: warning: format '%zd' expects argument of type 'signed size_t', but argument 4 has type 'ssize_t' [-Wformat]: => 372:4
>> + fs/quota/quota_v2.c: warning: format '%zd' expects argument of type 'signed size_t', but argument 5 has type 'ssize_t' [-Wformat]: => 66:92
> These really look like false positives (there are quite a few of this
> kind). Can we possibly silence them?
These 2 warnings happen on cris only, because size_t is unsigned int and
ssize_t is (signed) long. They go away if I make ssize_t int.
I had a look at the various definitions of size_t and ssize_t:
generic 32-bit: unsigned int int
generic 64-bit: __kernel_ulong_t (unsigned long)
avr32: unsigned long long
blackfin: unsigned long long
cris: __SIZE_TYPE__ (unsigned int) long
mn10300/__GNUC__ == 4: unsigned int signed int
mn10300/__GNUC__ != 4: unsigned long signed long
s390 (32-bit): unsigned long int
x32: __kernel_ulong_t (unsigned long long)
__kernel_long_t (long long)
On cris, I get the warning if ssize_t != int.
Whether size_t is unsigned int or unsigned long doesn't matter.
So it's not just a mismatch between int and long.
I also tried blackfin, which has matching unsigned long/long, and it doesn't
give the warning. Presumably the toolchain has size_t hardcoded to long for
printf-style format checking?
I haven't tried s390 yet, which also has a non-matching combination (unsigned
long vs. int).
Cris-people: __SIZE_TYPE__ turned out to be hardcoded in my compiler (gcc
4.6.3 from Tony's collection) to unsigned int. Is that correct?
And why do some 32-bit architectures use unsigned long/long?
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/