From: Mike Frysinger <vapier@gentoo.org>
To: linux-sparse@vger.kernel.org
Cc: michael.hennerich@analog.com
Subject: [PATCH] parser: add Blackfin gcc info
Date: Tue, 5 Oct 2010 04:34:30 -0400 [thread overview]
Message-ID: <1286267670-20974-1-git-send-email-vapier@gentoo.org> (raw)
The Blackfin port uses some custom attributes to control memory placement,
and it has some custom builtins. So add the ones that the kernel actually
utilizes to avoid massive build errors with sparse.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
---
lib.c | 3 +++
parse.c | 6 ++++++
2 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/lib.c b/lib.c
index ae6a20c..24176d8 100644
--- a/lib.c
+++ b/lib.c
@@ -716,6 +716,9 @@ void declare_builtin_functions(void)
add_pre_buffer("extern long __builtin_alpha_inslh(long, long);\n");
add_pre_buffer("extern long __builtin_alpha_cmpbge(long, long);\n");
add_pre_buffer("extern long __builtin_labs(long);\n");
+ add_pre_buffer("extern void __builtin_bfin_csync(void);\n");
+ add_pre_buffer("extern void __builtin_bfin_ssync(void);\n");
+ add_pre_buffer("extern int __builtin_bfin_norm_fr1x32(int);\n");
/* And some floating point stuff.. */
add_pre_buffer("extern int __builtin_isgreater(float, float);\n");
diff --git a/parse.c b/parse.c
index 9074b1d..32d2d0a 100644
--- a/parse.c
+++ b/parse.c
@@ -515,6 +515,12 @@ const char *ignored_attributes[] = {
"__format_arg__",
"hot",
"__hot__",
+ "l1_text",
+ "__l1_text__",
+ "l1_data",
+ "__l1_data__",
+ "l2",
+ "__l2__",
"malloc",
"__malloc__",
"may_alias",
--
1.7.3.1
next reply other threads:[~2010-10-05 8:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 8:34 Mike Frysinger [this message]
2010-10-05 16:18 ` [PATCH] parser: add Blackfin gcc info Josh Triplett
2010-10-06 1:34 ` Mike Frysinger
2010-10-06 2:33 ` Christopher Li
2010-10-06 5:38 ` Mike Frysinger
2010-10-06 7:10 ` Josh Triplett
2010-10-06 8:40 ` Christopher Li
2010-10-06 14:52 ` Mike Frysinger
2010-10-06 16:32 ` Mike Frysinger
2010-10-06 21:14 ` Christopher Li
2010-10-06 7:05 ` 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=1286267670-20974-1-git-send-email-vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=linux-sparse@vger.kernel.org \
--cc=michael.hennerich@analog.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).