From: Pekka Enberg <penberg@kernel.org>
To: linux-sparse@vger.kernel.org
Cc: Pekka Enberg <penberg@kernel.org>,
Christopher Li <sparse@chrisli.org>,
Jeff Garzik <jgarzik@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: [PATCH] sparse, llvm: Fix symbol_type() for bitfields and enums
Date: Tue, 25 Oct 2011 11:59:16 +0300 [thread overview]
Message-ID: <1319533156-2765-1-git-send-email-penberg@kernel.org> (raw)
This patch adds SYM_BITFIELD and SYM_ENUM support to symbol_type().
Cc: Christopher Li <sparse@chrisli.org>
Cc: Jeff Garzik <jgarzik@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Pekka Enberg <penberg@kernel.org>
---
sparse-llvm.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/sparse-llvm.c b/sparse-llvm.c
index 5d1b79c..9f4586f 100644
--- a/sparse-llvm.c
+++ b/sparse-llvm.c
@@ -121,6 +121,8 @@ static LLVMTypeRef symbol_type(LLVMModuleRef module, struct symbol *sym)
LLVMTypeRef ret = NULL;
switch (sym->type) {
+ case SYM_BITFIELD:
+ case SYM_ENUM:
case SYM_NODE:
ret = symbol_type(module, sym->ctype.base_type);
break;
--
1.7.6.4
reply other threads:[~2011-10-25 8:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1319533156-2765-1-git-send-email-penberg@kernel.org \
--to=penberg@kernel.org \
--cc=jgarzik@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
--cc=torvalds@linux-foundation.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).