Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: gcc 4.9 build warnings (was: Re: arm-soc build: 2917 warnings 0 failures (arm-soc/v3.18-rc1-20-g06c0773))
Date: Thu, 06 Nov 2014 12:56:27 +0100	[thread overview]
Message-ID: <2700572.p8cKrIiMH5@wuerfel> (raw)
In-Reply-To: <20141106114919.GL26297@ulmo>

On Thursday 06 November 2014 12:49:22 Thierry Reding wrote:
> GCC complains about the format specifier being wrong. %zu/%zd are the
> correct specifiers for variables of type size_t/ssize_t, so wherever a
> size_t or ssize_t is used as parameter it should have a corresponding
> %zu or %zd specifier.
> 
> Why not just fix it properly instead of mucking about with the size_t
> typedef?
> 

Yes, but where are %zu and %zd implemented in gcc? I've looked but
couldn't find it. For all I can tell is that gcc's own interpretation
of %z doesn't match its definition of __SIZE_TYPE__ when building for
bare-metal.

	Arnd

  reply	other threads:[~2014-11-06 11:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <544a2a2e.a2db440a.6eeb.ffffaef3@mx.google.com>
2014-10-24 10:49 ` gcc 4.9 build warnings (was: Re: arm-soc build: 2917 warnings 0 failures (arm-soc/v3.18-rc1-20-g06c0773)) Arnd Bergmann
2014-10-24 10:52   ` Russell King - ARM Linux
2014-10-24 10:59     ` Ard Biesheuvel
2014-10-24 11:37       ` Arnd Bergmann
2014-10-24 11:50         ` Ard Biesheuvel
2014-10-24 13:27           ` Arnd Bergmann
2014-10-24 13:41             ` Ard Biesheuvel
2014-11-06 11:49               ` Thierry Reding
2014-11-06 11:56                 ` Arnd Bergmann [this message]
2014-11-06 12:59                   ` Thierry Reding
2014-11-06 13:08                     ` Ard Biesheuvel
2014-11-06 13:16                       ` Thierry Reding
2014-11-06 13:20                       ` Arnd Bergmann
2014-11-06 13:28                 ` Russell King - ARM Linux
2014-11-06 13:58                   ` Mark Brown

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=2700572.p8cKrIiMH5@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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