From: Michael Stefaniuc <mstefaniuc@gmail.com>
To: linux-sparse@vger.kernel.org
Subject: [PATCH] Ignore the alloc_size attribute.
Date: Wed, 30 Sep 2009 22:19:30 +0200 [thread overview]
Message-ID: <20090930201930.GB32461@redhat.com> (raw)
Wine has annotated the Win32 alloc functions with the alloc_size
attribute. This cuts down the noise a lot when running sparse on the
Wine source code.
Signed-off-by: Michael Stefaniuc <mstefaniuc@gmail.com>
---
Resend for the chrisl tree.
parse.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/parse.c b/parse.c
index fa3b45e..c3f9b6a 100644
--- a/parse.c
+++ b/parse.c
@@ -475,6 +475,8 @@ static struct init_keyword {
const char *ignored_attributes[] = {
"alias",
"__alias__",
+ "alloc_size",
+ "__alloc_size__",
"always_inline",
"__always_inline__",
"bounded",
--
1.6.5.rc2
next reply other threads:[~2009-09-30 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 20:19 Michael Stefaniuc [this message]
2009-09-30 21:02 ` [PATCH] Ignore the alloc_size attribute Christopher Li
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=20090930201930.GB32461@redhat.com \
--to=mstefaniuc@gmail.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).