From: Lance Richardson <lrichard@redhat.com>
To: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: bit-field notation and k&r function syntax
Date: Wed, 3 May 2017 13:10:12 -0400 (EDT) [thread overview]
Message-ID: <571546431.4485670.1493831412428.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1231012108.4484627.1493830970281.JavaMail.zimbra@redhat.com>
I noticed when browsing parse.c that function parameters declared
using K&R syntax are parsed by calling declaration_list(), which
seems to have been intended for parsing structure member declarations
and accepts bit-field syntax.
So e.g. this is (incorrectly) accepted by sparse:
static int foo(b)
int b: 4;
{
return 0;
}
next parent reply other threads:[~2017-05-03 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1231012108.4484627.1493830970281.JavaMail.zimbra@redhat.com>
2017-05-03 17:10 ` Lance Richardson [this message]
2017-05-03 23:07 ` bit-field notation and k&r function syntax Luc Van Oostenryck
2017-05-04 1:50 ` Christopher Li
2017-05-04 2:14 ` Luc Van Oostenryck
2017-05-04 3:20 ` Christopher Li
2017-05-04 15:07 ` Luc Van Oostenryck
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=571546431.4485670.1493831412428.JavaMail.zimbra@redhat.com \
--to=lrichard@redhat.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).