linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Derek M Jones <derek@knosof.co.uk>
Cc: Josh Triplett <josht@linux.vnet.ibm.com>,
	Alexey Dobriyan <adobriyan@sw.ru>,
	linux-sparse@vger.kernel.org, adobriyan@gmail.com
Subject: Re: declaration specifiers wooziness
Date: Wed, 27 Jun 2007 16:39:27 +0100	[thread overview]
Message-ID: <20070627153927.GV21478@ftp.linux.org.uk> (raw)
In-Reply-To: <46827F4D.7010305@knosof.co.uk>

On Wed, Jun 27, 2007 at 04:16:29PM +0100, Derek M Jones wrote:

> These are all permitted by the syntax of C.
> 
> 6.7 Declarations, the init-declarator-list is optional.

See 6.7[2]; the things like
	int ;
violate the constraint.
 
> >>"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.

See 6.7.1[2]; no more than one storage class specifier in a declaration.

> >Several more:
> 
> The syntax permits:
> 
> signed unsigned short long double int;

See 6.7.2[2]; the set you've given is not in the list given there.

  parent reply	other threads:[~2007-06-27 15:40 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
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 [this message]
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=20070627153927.GV21478@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=adobriyan@gmail.com \
    --cc=adobriyan@sw.ru \
    --cc=derek@knosof.co.uk \
    --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).