public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Keith.S.Thompson at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/54486] New: Spurious printf format warning mentions nonexistent type 'sizetype' Date: Wed, 05 Sep 2012 00:28:00 -0000 [thread overview] Message-ID: <bug-54486-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54486 Bug #: 54486 Summary: Spurious printf format warning mentions nonexistent type 'sizetype' Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: Keith.S.Thompson@gmail.com printf's "%zu" format expects an argument of type size_t. In the sample program, the corresponding argument is of type size_t in all the printf calls (the first because strspn() is defined to return a size_t result, and the second because of the explicit cast, and similarly for the others). For a call to strlen() or to a user-defined function func(), gcc rightly does not complain. For a call to strspn(), even with an explicit cast, gcc incorrectly complains that the arguments is of type ‘sizetype’ -- which, as far as I can tell, doesn't exist. (If I try to add a variable definition of type ‘sizetype’, I get "error: unknown type name ‘sizetype’", and I can find no reference to ‘sizetype’ in any of my system's headers.) I see nothing unusual in the declaration of strspn() in /usr/include/string.h. $ uname -a Linux kvetch 3.2.0-29-generic-pae #46-Ubuntu SMP Fri Jul 27 17:25:43 UTC 2012 i686 i686 i386 GNU/Linux $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.10 DISTRIB_CODENAME=quantal DISTRIB_DESCRIPTION="Ubuntu quantal (development branch)" $ gcc --version gcc (Ubuntu/Linaro 4.7.0-7ubuntu3) 4.7.0 Copyright (C) 2012 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. $ cat c.c #include <string.h> #include <stdio.h> extern size_t func(void); int main(void) { printf("%zu\n", strspn("abc", "abcdefg")); /* line 7 */ printf("%zu\n", (size_t)strspn("abc", "abcdefg")); /* line 8 */ printf("%zu\n", strlen("foo")); printf("%zu\n", (size_t)strlen("foo")); printf("%zu\n", func()); printf("%zu\n", (size_t)func()); return 0; } $ gcc -c -std=c99 -pedantic c.c c.c: In function ‘main’: c.c:7:5: warning: format ‘%zu’ expects argument of type ‘size_t’, but argument 2 has type ‘sizetype’ [-Wformat] c.c:8:5: warning: format ‘%zu’ expects argument of type ‘size_t’, but argument 2 has type ‘sizetype’ [-Wformat] $
next reply other threads:[~2012-09-05 0:28 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-05 0:28 Keith.S.Thompson at gmail dot com [this message] 2012-09-05 6:05 ` [Bug c/54486] " polacek at redhat dot com 2012-09-05 6:13 ` pinskia at gcc dot gnu.org 2012-09-05 6:18 ` jakub at gcc dot gnu.org 2012-09-05 7:13 ` [Bug middle-end/54486] [4.6/4.7/4.8 Regression] " jakub at gcc dot gnu.org 2012-09-05 16:28 ` jakub at gcc dot gnu.org 2012-09-05 16:30 ` jakub at gcc dot gnu.org 2012-09-07 10:50 ` [Bug middle-end/54486] [4.6 " rguenth at gcc dot gnu.org 2013-04-03 18:19 ` jakub at gcc dot gnu.org
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=bug-54486-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).