From: Pavel Roskin <proski@gnu.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-sparse@vger.kernel.org
Subject: Re: Bogus locking warnings
Date: Tue, 27 Feb 2007 02:24:26 -0500 [thread overview]
Message-ID: <1172561066.19312.28.camel@dv> (raw)
In-Reply-To: <Pine.LNX.4.64.0702262000460.12485@woody.linux-foundation.org>
On Mon, 2007-02-26 at 20:19 -0800, Linus Torvalds wrote:
> and don't expect sparse to do any dynamic checking. It's expressly
> designed to *not* do that, although some of the static optimizations
> are
> clever enough that sometimes you are fooled into *thinking* that it
> actually understands dynamic behaviour (ie being able to statically
> follow
> a conditional jump to another identical conditional jump and simplify
> it
> to a single branch).
It has been fooling me until now. Anyway, thanks for the detailed
answer! I'll try to do what you are suggesting.
--
Regards,
Pavel Roskin
prev parent reply other threads:[~2007-02-27 7:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 1:42 Bogus locking warnings Pavel Roskin
2007-02-27 4:19 ` Linus Torvalds
2007-02-27 7:24 ` Pavel Roskin [this message]
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=1172561066.19312.28.camel@dv \
--to=proski@gnu.org \
--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