From: Derek M Jones <derek@knosof.co.uk>
To: Josh Triplett <josht@linux.vnet.ibm.com>
Cc: Alexey Dobriyan <adobriyan@sw.ru>,
linux-sparse@vger.kernel.org, adobriyan@gmail.com
Subject: Re: declaration specifiers wooziness
Date: Wed, 27 Jun 2007 16:16:29 +0100 [thread overview]
Message-ID: <46827F4D.7010305@knosof.co.uk> (raw)
In-Reply-To: <1182956472.8970.35.camel@josh-work.beaverton.ibm.com>
Alex, Josh,
> On Wed, 2007-06-27 at 14:33 +0400, Alexey Dobriyan wrote:
>> sparse silently accepts some peculiar combinations of declaration
>> specifiers:
These are all permitted by the syntax of C.
6.7 Declarations, the init-declarator-list is optional.
>> "typedef extern;" passes.
...
>> Not sure how many different bugs there are here, though...
Sparse might flag the usage as suspicious, but it is not a bug.
> Several more:
The syntax permits:
signed unsigned short long double int;
>
> int;
> void;
> int *;
> void *;
> static;
> extern;
> volatile;
> static foo;
> extern foo;
> volatile foo;
> int volatile;
>
> - Josh Triplett
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Derek M. Jones tel: +44 (0) 1252 520 667
Knowledge Software Ltd mailto:derek@knosof.co.uk
Applications Standards Conformance Testing http://www.knosof.co.uk
next prev parent reply other threads:[~2007-06-27 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 10:33 declaration specifiers wooziness Alexey Dobriyan
2007-06-27 15:01 ` Josh Triplett
2007-06-27 15:16 ` Derek M Jones [this message]
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=46827F4D.7010305@knosof.co.uk \
--to=derek@knosof.co.uk \
--cc=adobriyan@gmail.com \
--cc=adobriyan@sw.ru \
--cc=josht@linux.vnet.ibm.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).