From: Josh Triplett <josh@freedesktop.org>
To: Christopher Li <sparse@chrisli.org>
Cc: Pavel Roskin <proski@gnu.org>, linux-sparse@vger.kernel.org
Subject: Re: [PATCH](take II) Sparse fooled by double semicolon
Date: Thu, 22 Feb 2007 19:43:29 -0800 [thread overview]
Message-ID: <45DE62E1.9040606@freedesktop.org> (raw)
In-Reply-To: <20070131071717.GA23495@chrisli.org>
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
Christopher Li wrote:
> Actually, this version is better because it handle semicolon
> as the first member as well.
>
> Fix double semicolon in struct declare
>
> Pavel discover this test case:
> #include <string.h>
> void test(void)
> {
> struct { int foo;; } val;
> memset(&val, 0, sizeof(val));
> }
>
> Sparse ends up create a node with empty ctype in the member list.
> Skip that seems fix it.
>
> Signed-Off-By: Christopher Li<spase@chrisli.org>
Applied, along with the test case.
- Josh Triplett
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2007-02-23 3:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 4:50 Sparse fooled by double semicolon Pavel Roskin
2007-01-31 6:58 ` [PATCH] " Christopher Li
2007-01-31 7:17 ` [PATCH](take II) " Christopher Li
2007-01-31 7:46 ` Pavel Roskin
2007-02-23 3:43 ` Josh Triplett [this message]
2007-01-31 7:43 ` [PATCH] " Pavel Roskin
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=45DE62E1.9040606@freedesktop.org \
--to=josh@freedesktop.org \
--cc=linux-sparse@vger.kernel.org \
--cc=proski@gnu.org \
--cc=sparse@chrisli.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).