Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Josh Triplett <josh@freedesktop.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Christopher Li <sparse@chrisli.org>,
	Anton Altaparmakov <aia21@cam.ac.uk>,
	linux-sparse@vger.kernel.org
Subject: Re: Bogus sparse warning?
Date: Tue, 13 Feb 2007 00:30:58 -0800	[thread overview]
Message-ID: <45D17742.4010809@freedesktop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0702121147170.8424@woody.linux-foundation.org>

[-- Attachment #1: Type: text/plain, Size: 1159 bytes --]

Linus Torvalds wrote:
> On Mon, 12 Feb 2007, Christopher Li wrote:
>> On Mon, Feb 12, 2007 at 10:28:19AM -0800, Linus Torvalds wrote:
>>> (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.
> 
> Ahh. 
> 
>> 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.
> 
> This looks good. Ack.  Josh?

See my response to Christopher later in the thread; his revised patch appears
to solve the problem fully.

> The only thing that I reacted to is that maybe we should change the
> 
> 	s->ctype.modifiers = 0;
> 
> a few lines down into a
> 
> 	s->ctype.modifiers &= ~MOD_PTRINHERIT;
> 
> or something?

Christopher's revised patch does exactly that.

- Josh Triplett


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2007-02-13  8:31 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
2007-02-12 19:53     ` Linus Torvalds
2007-02-13  8:30       ` Josh Triplett [this message]
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=45D17742.4010809@freedesktop.org \
    --to=josh@freedesktop.org \
    --cc=aia21@cam.ac.uk \
    --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