From: Emil Medve <Emilian.Medve@Freescale.com>
To: josh@freedesktop.org, linux-sparse@vger.kernel.org
Cc: Emil Medve <Emilian.Medve@Freescale.com>
Subject: [PATCH] Handle ignored attribute malloc
Date: Thu, 25 Oct 2007 16:12:49 -0500 [thread overview]
Message-ID: <1193346769-18030-1-git-send-email-Emilian.Medve@Freescale.com> (raw)
This avoids error messages like this:
error: attribute 'malloc': unknown attribute
Signed-off-by: Emil Medve <Emilian.Medve@Freescale.com>
---
Please copy me in replies as I'm not subscribed to the list
ident-list.h | 1 +
parse.c | 1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/ident-list.h b/ident-list.h
index b183eac..8fcd7de 100644
--- a/ident-list.h
+++ b/ident-list.h
@@ -69,6 +69,7 @@ IDENT(model); IDENT(__model__);
IDENT(format_arg); IDENT(__format_arg__);
IDENT(nothrow); IDENT(__nothrow); IDENT(__nothrow__);
IDENT(__transparent_union__);
+IDENT(malloc);
IDENT(__malloc__);
IDENT(nonnull); IDENT(__nonnull); IDENT(__nonnull__);
IDENT(constructor); IDENT(__constructor__);
diff --git a/parse.c b/parse.c
index 47b5204..a41939d 100644
--- a/parse.c
+++ b/parse.c
@@ -283,6 +283,7 @@ static struct init_keyword {
{ "nothrow", NS_KEYWORD, .op = &ignore_attr_op },
{ "__nothrow", NS_KEYWORD, .op = &ignore_attr_op },
{ "__nothrow__", NS_KEYWORD, .op = &ignore_attr_op },
+ { "malloc", NS_KEYWORD, .op = &ignore_attr_op },
{ "__malloc__", NS_KEYWORD, .op = &ignore_attr_op },
{ "nonnull", NS_KEYWORD, .op = &ignore_attr_op },
{ "__nonnull", NS_KEYWORD, .op = &ignore_attr_op },
--
1.5.3.GIT
next reply other threads:[~2007-10-25 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 21:12 Emil Medve [this message]
2007-10-26 3:16 ` [PATCH] Handle ignored attribute malloc Christopher Li
2007-10-26 20:11 ` Medve Emilian-EMMEDVE1
2007-11-13 12:13 ` Josh Triplett
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=1193346769-18030-1-git-send-email-Emilian.Medve@Freescale.com \
--to=emilian.medve@freescale.com \
--cc=josh@freedesktop.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).