From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Dave Olien <dmo@osdl.org>
Cc: Petri Koistinen <petri.koistinen@iki.fi>, linux-kernel@vger.kernel.org
Subject: Re: Sparse warning: bitmap.h: bad constant expression
Date: Tue, 2 Sep 2003 22:11:50 +0200 [thread overview]
Message-ID: <20030902201150.GC24744@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20030902173844.GA20578@osdl.org>
On Tue, 2 September 2003 10:38:44 -0700, Dave Olien wrote:
>
> I was lazy with my problem summary yesterday. The sparse warning is actually
> about the declaration of the functions bitmap_shift_right() and
> bitmap_shift_left() in bitmap.h. In these cases, the bits argument to
> DECLARE_BITMAP() was an argument to the function, and th variable sized
> array is in the scope of that function.
>
> The only uses of these functions I can find are in the macros
> physids_shift_right, physids_shift_left, in mpsec.h, and cpus_shift_rigt
> and cpus_shift_left, in cpumask_array.h.
>
> In all uses, the "bits" argument eventually resolves to being a constant.
> It would require the inline expansion of the bitmap_shift_*() functions
> to take advantage of that.
If your analysis is correct, this looks safe enough for now. It would
be nice to replace it with something more explicit, but I just don't
care enough yet.
Jörn
--
Fantasy is more important than knowlegde. Knowlegde is limited,
while fantasy embraces the whole world.
-- Albert Einstein
next prev parent reply other threads:[~2003-09-02 20:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 19:59 Petri Koistinen
2003-09-02 1:57 ` Dave Olien
2003-09-02 9:56 ` Jörn Engel
2003-09-02 10:23 ` Mikael Pettersson
2003-09-02 10:54 ` Jörn Engel
2003-09-02 16:45 ` Linus Torvalds
2003-09-02 20:08 ` Jörn Engel
2003-09-02 17:38 ` Dave Olien
2003-09-02 20:11 ` Jörn Engel [this message]
2003-09-02 17:22 ` William Lee Irwin III
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=20030902201150.GC24744@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=dmo@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petri.koistinen@iki.fi \
/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
all inboxes | Powered by JetHome®