From: Christopher Li <sparse@chrisli.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Anton Altaparmakov <aia21@cam.ac.uk>, linux-sparse@vger.kernel.org
Subject: Re: Bogus sparse warning?
Date: Mon, 12 Feb 2007 11:14:34 -0800 [thread overview]
Message-ID: <20070212191434.GA1041@chrisli.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702121018270.8424@woody.linux-foundation.org>
On Mon, Feb 12, 2007 at 10:28:19AM -0800, Linus Torvalds wrote:
>
>
> > From <include/linux/fs.h>:
> >
> > typedef int (get_block_t)(struct inode *inode, sector_t iblock,
> > struct buffer_head *bh_result, int create);
>
> so that it looks like
>
> typedef int (*get_block_t)(...)
>
> instead?
>
> (It is perfectly proper to have a typedef that is actually of a function
> type, so this looks like a sparse bug regardless, it looks just as if we
> don't turn a function type into a function pointer type when we see it as
> an argument in the declaration).
Yes, we does, in examine_fn_arguments(). But not correctly inherent the attribute bits.
>
> Has this been there for a long time, or was it something recent in sparse
> that seemed to trigger it (like the recent ctype conversion changes due to
> attribute parsing?)
I think this patch should fix it, I haven't try it myself on this bug yet.
It works on a different test case "function vs function ptr".
It has been posted to the list before. It is in my series as well.
Chris
Index: sparse/symbol.h
===================================================================
--- sparse.orig/symbol.h 2007-02-04 23:46:07.000000000 -0800
+++ sparse/symbol.h 2007-02-05 12:18:30.000000000 -0800
@@ -191,6 +191,7 @@ struct symbol {
#define MOD_SIZE (MOD_CHAR | MOD_SHORT | MOD_LONG | MOD_LONGLONG)
#define MOD_IGNORE (MOD_TOPLEVEL | MOD_STORAGE | MOD_ADDRESSABLE | \
MOD_ASSIGNED | MOD_USERTYPE | MOD_FORCE | MOD_ACCESSED | MOD_EXPLICITLY_SIGNED)
+#define MOD_PTRINHERIT (MOD_VOLATILE | MOD_CONST | MOD_NODEREF | MOD_STORAGE)
/* Current parsing/evaluation function */
Index: sparse/evaluate.c
===================================================================
--- sparse.orig/evaluate.c 2007-02-04 00:47:46.000000000 -0800
+++ sparse/evaluate.c 2007-02-05 12:20:08.000000000 -0800
@@ -1282,7 +1282,7 @@ static void examine_fn_arguments(struct
else
ptr->ctype.base_type = arg;
ptr->ctype.as |= s->ctype.as;
- ptr->ctype.modifiers |= s->ctype.modifiers;
+ ptr->ctype.modifiers |= s->ctype.modifiers & MOD_PTRINHERIT;
s->ctype.base_type = ptr;
s->ctype.as = 0;
@@ -1313,8 +1313,6 @@ static struct symbol *convert_to_as_mod(
return sym;
}
-#define MOD_PTRINHERIT (MOD_VOLATILE | MOD_CONST | MOD_NODEREF | MOD_STORAGE)
-
static struct symbol *create_pointer(struct expression *expr, struct symbol *sym, int degenerate)
{
struct symbol *node = alloc_symbol(expr->pos, SYM_NODE);
next prev parent reply other threads:[~2007-02-12 19:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 10:05 Bogus sparse warning? Anton Altaparmakov
2007-02-12 18:28 ` Linus Torvalds
2007-02-12 19:14 ` Christopher Li [this message]
2007-02-12 19:53 ` Linus Torvalds
2007-02-13 8:30 ` Josh Triplett
2007-02-13 0:15 ` Anton Altaparmakov
2007-02-13 1:46 ` Christopher Li
2007-02-13 8:22 ` Josh Triplett
[not found] ` <20070213190400.GA9989@chrisli.org>
2007-02-13 23:01 ` Josh Triplett
2007-02-13 9:39 ` Anton Altaparmakov
2007-02-13 0:25 ` Anton Altaparmakov
2007-02-13 0:42 ` Linus Torvalds
2007-02-13 9:53 ` Anton Altaparmakov
2007-02-13 16:10 ` Linus Torvalds
2007-02-13 21:23 ` Anton Altaparmakov
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=20070212191434.GA1041@chrisli.org \
--to=sparse@chrisli.org \
--cc=aia21@cam.ac.uk \
--cc=linux-sparse@vger.kernel.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