mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@xenotime.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: Build regressions/improvements in v3.0-rc5 (ssize_t ???)
Date: Wed, 29 Jun 2011 14:06:30 -0700	[thread overview]
Message-ID: <20110629140630.5aefdda8.rdunlap@xenotime.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1106291011400.10665@ayla.of.borg>

On Wed, 29 Jun 2011 10:13:17 +0200 (CEST) Geert Uytterhoeven wrote:

> *** WARNINGS ***
> 
> 358 regressions:

>   + drivers/net/wimax/i2400m/usb-fw.c: warning: format '%zd' expects type 'signed size_t', but argument 4 has type 'ssize_t':  => 210
>   + drivers/net/wimax/i2400m/usb-fw.c: warning: format '%zd' expects type 'signed size_t', but argument 8 has type 'ssize_t':  => 222

>   + drivers/staging/bcm/Bcmchar.c: warning: format '%zd' expects type 'signed size_t', but argument 2 has type 'ssize_t':  => 146
>   + drivers/staging/bcm/Bcmchar.c: warning: format '%zd' expects type 'signed size_t', but argument 3 has type 'ssize_t':  => 146

>   + net/sunrpc/auth_gss/auth_gss.c: warning: format '%Zd' expects type 'signed size_t', but argument 2 has type 'ssize_t':  => 708
>   + net/sunrpc/auth_gss/auth_gss.c: warning: format '%zd' expects type 'signed size_t', but argument 3 has type 'ssize_t':  => 690


Can someone explain these warnings, please?  (signed size_t vs. ssize_t)

Is gcc confused?
Looks like a compiler issue to me.

thanks,
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

  parent reply	other threads:[~2011-06-29 21:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29  8:13 Build regressions/improvements in v3.0-rc5 Geert Uytterhoeven
2011-06-29 21:06 ` Build regressions/improvements in v3.0-rc5 (arch/cris) Randy Dunlap
2011-06-30  8:23   ` Américo Wang
2011-06-29 21:06 ` Randy Dunlap [this message]
2011-06-30  6:59   ` Build regressions/improvements in v3.0-rc5 (ssize_t ???) Geert Uytterhoeven
2011-06-30  7:16     ` Mikael Starvik
2011-06-30  8:01     ` Christoph Hellwig
2011-06-30  8:43       ` Geert Uytterhoeven
2011-06-30  8:56         ` Christoph Hellwig
2011-06-30  9:32           ` Geert Uytterhoeven
2011-06-30  9:44             ` Christoph Hellwig
2011-06-30 17:07         ` Andreas Schwab
2011-07-01  5:25           ` Mikael Starvik
2011-07-01  8:34             ` Andreas Schwab
2011-06-30 16:12     ` Randy Dunlap
2011-06-29 21:21 ` Build regressions/improvements in v3.0-rc5 (xfs on cris) Randy Dunlap
2011-06-29 21:24   ` Christoph Hellwig
2011-06-30  8:34     ` Américo Wang
2011-07-01 22:05 ` Build regressions/improvements in v3.0-rc5 Arnd Bergmann
2011-07-01 23:15   ` Mike Frysinger
2011-07-02  8:38     ` Arnd Bergmann

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=20110629140630.5aefdda8.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    /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
all inboxes | Powered by JetHome®