From: Pavel Roskin <proski@gnu.org>
To: linux-sparse@vger.kernel.org
Subject: Sparse fooled by double semicolon
Date: Tue, 30 Jan 2007 23:50:27 -0500 [thread overview]
Message-ID: <1170219027.11455.68.camel@dv> (raw)
Hello!
I have reduced a spurious sparse message to the following test:
#include <string.h>
void test(void)
{
struct { int foo;; } val;
memset(&val, 0, sizeof(val));
}
Running sparse on this code gives:
test.c:5:8: warning: memset with byte count of 0
Replacing two semicolons with one fixes the warning. That's the current
sparse (006eff06c7adcfb0d06c6fadf6e9b64f0488b2bf) with no local changes.
--
Regards,
Pavel Roskin
next reply other threads:[~2007-01-31 4:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 4:50 Pavel Roskin [this message]
2007-01-31 6:58 ` [PATCH] Sparse fooled by double semicolon 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
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=1170219027.11455.68.camel@dv \
--to=proski@gnu.org \
--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).