[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F4D663D.2040100@xenotime.net>
Date: Tue, 28 Feb 2012 15:41:49 -0800
From: Randy Dunlap <rdunlap@...otime.net>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
CC: linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
Al Viro <viro@...iv.linux.org.uk>
Subject: Re: Build regressions/improvements in v3.3-rc5 (C lang questions)
On 02/28/2012 12:50 PM, Geert Uytterhoeven wrote:
> Below is the list of build error/warning regressions/improvements in
> v3.3-rc5[1] compared to v3.2[2].
> + src/drivers/usb/misc/sisusbvga/sisusb.c: warning: format '%zd' expects type 'signed size_t', but argument 3 has type 'ssize_t': => 982
> + src/fs/ecryptfs/miscdev.c: warning: format '%zd' expects type 'signed size_t', but argument 3 has type 'ssize_t': => 448, 488
Do the (2) above mean that some platform's gcc is borked?
(I don't see these on i386 or x86_64.)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> + src/fs/ecryptfs/miscdev.c: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'unsigned int': => 433, 433:60
I can see that warning on 32-bit i386 (X86_32), but if I change the
"%lu" to "%u", it causes this warning on 64-bit x86_64:
fs/ecryptfs/miscdev.c:433:38: warning: format '%u' expects type 'unsigned int', but argument 4 has type 'long unsigned int'
so how is this supposed to be handled?
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists