All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: Build regressions/improvements in v3.3-rc5 (C lang questions)
Date: Tue, 28 Feb 2012 15:41:49 -0800	[thread overview]
Message-ID: <4F4D663D.2040100@xenotime.net> (raw)
In-Reply-To: <1330462222-25201-1-git-send-email-geert@linux-m68k.org>

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.


  reply	other threads:[~2012-02-28 23:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 20:50 Build regressions/improvements in v3.3-rc5 Geert Uytterhoeven
2012-02-28 23:41 ` Randy Dunlap [this message]
2012-02-29  0:08   ` Build regressions/improvements in v3.3-rc5 (C lang questions) Linus Torvalds
2012-02-29  0:24     ` Randy Dunlap
2012-02-29  0:31       ` [PATCH] ecryptfs: fix printk format warning for size_t Randy Dunlap

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=4F4D663D.2040100@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.