From: Christopher Li <sparse@chrisli.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Lance Richardson <lrichard@redhat.com>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: bit-field notation and k&r function syntax
Date: Wed, 3 May 2017 21:50:14 -0400 [thread overview]
Message-ID: <CANeU7Qn+R5auoxi=-==W+uExRfE7wRc7pfK-5OcENVEaB1-9Hw@mail.gmail.com> (raw)
In-Reply-To: <20170503230721.vb4aunmpaa2xxaf2@desk.local>
On Wed, May 3, 2017 at 7:07 PM, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
> What's sparse use 'declaration_list()' for is not what correspond
> to the standard's 'declaration-list' but is indeed for something
> that should be reserved to structs.
I think declaration_list() can add one argument "is_struct" to
indicate parse for struct or not.
Only in struct mode we do the ":" and handle_bitfield() thing.
There are only two caller of declaration_list() so that should fix it.
Chris
next prev parent reply other threads:[~2017-05-04 1:50 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 ` bit-field notation and k&r function syntax Lance Richardson
2017-05-03 23:07 ` Luc Van Oostenryck
2017-05-04 1:50 ` Christopher Li [this message]
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='CANeU7Qn+R5auoxi=-==W+uExRfE7wRc7pfK-5OcENVEaB1-9Hw@mail.gmail.com' \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=lrichard@redhat.com \
--cc=luc.vanoostenryck@gmail.com \
/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).