From: Alexey Dobriyan <adobriyan@sw.ru>
To: linux-sparse@vger.kernel.org
Cc: adobriyan@gmail.com
Subject: declaration specifiers wooziness
Date: Wed, 27 Jun 2007 14:33:20 +0400 [thread overview]
Message-ID: <20070627103320.GA11047@localhost.sw.ru> (raw)
sparse silently accepts some peculiar combinations of declaration
specifiers:
"typedef extern;" passes.
"void char a;" errors about void declaration, however,
"extern void char a;" passes. Hey, "extern void a;" passes!
"char short a;" passes too. Ditto for "char float a;" and
"char long a".
"typedef inline a;" passes.
Not sure how many different bugs there are here, though...
next reply other threads:[~2007-06-27 10:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 10:33 Alexey Dobriyan [this message]
2007-06-27 15:01 ` declaration specifiers wooziness Josh Triplett
2007-06-27 15:16 ` Derek M Jones
2007-06-27 15:31 ` Alexey Dobriyan
2007-06-27 15:34 ` Derek M Jones
2007-06-27 15:44 ` Derek M Jones
2007-06-27 15:48 ` Josh Triplett
2007-06-27 16:00 ` Al Viro
2007-06-27 15:39 ` Al Viro
2007-06-27 15:39 ` Josh Triplett
2007-06-27 15:41 ` Al Viro
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=20070627103320.GA11047@localhost.sw.ru \
--to=adobriyan@sw.ru \
--cc=adobriyan@gmail.com \
--cc=linux-sparse@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;
as well as URLs for NNTP newsgroup(s).