From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Andrew Murray <amurray@mpc-data.co.uk>,
linux-m68k@lists.linux-m68k.org
Subject: [Question] How to print size_t type variable?
Date: Mon, 15 Dec 2014 18:32:18 +0900 [thread overview]
Message-ID: <20141215183217.0529.AA925319@jp.panasonic.com> (raw)
Hi experts,
I read through Documentation/printk-formats.txt
It clearly says to use "%zu" or "%zx" to print size_t variables,
but I still have a question.
Assume we have code something like:
printk("%zx", (size_t)10);
I think this code works fine as long as it includes
the compiler-provided <stddef.h>.
In the kernel space, however, <stddef.h> is never included.
Instead, size_t is defined by include/linux/types.h
and include/uapi/asm-generic/posix_types.h.
That is, size_t is defined independently from the compiler you are using,
although the compiler still decides which variable type is expected for the "%zx" format.
This causes compiler warnings for some compilers.
On bare-metal m68k toolchains, for example, size_t is "unsignd long",
whearas it is "unsigned int" on kernel.org m68k toolchains.
I see such warnings when I built the kernel with bare-metal m68k toolchains.
$ git describe
v3.18
$ make ARCH=m68k CROSS_COMPILE=m68k-elf- defconfig all
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/zconf.lex.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
*** Default configuration is based on 'multi_defconfig'
kernel/time/Kconfig:163:warning: range is invalid
#
# configuration written to .config
#
[ snip ]
LD init/mounts.o
CC init/initramfs.o
init/initramfs.c: In function 'populate_rootfs':
init/initramfs.c:635:5: warning: format '%zd' expects argument of type 'signed size_t', but argument 2 has type 'ssize_t' [-Wformat]
Any advice?
How to fix this issue?
Best Regards
Masahiro Yamada
next reply other threads:[~2014-12-15 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 9:32 Masahiro Yamada [this message]
2014-12-15 9:38 ` [Question] How to print size_t type variable? Geert Uytterhoeven
[not found] ` <CAMuHMdWOAWr40YOoOVRvV-gPUU+ioSnShzHYcMoGpvhUO6chXw@mail.gmail.com>
2014-12-15 10:51 ` Masahiro Yamada
2014-12-15 11:00 ` Geert Uytterhoeven
[not found] ` <CAMuHMdUaSOr2iDHzWhkKXwwxdvHhpL1C_UR_tw9B1ALhebbdtQ@mail.gmail.com>
2014-12-16 3:05 ` Masahiro Yamada
2014-12-16 9:50 ` Geert Uytterhoeven
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=20141215183217.0529.AA925319@jp.panasonic.com \
--to=yamada.m@jp.panasonic.com \
--cc=amurray@mpc-data.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=rdunlap@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