From: Dave Jones <davej@redhat.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: linux-kernel@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: sparse warnings for variable length arrays
Date: Thu, 13 Jul 2006 13:01:27 -0400 [thread overview]
Message-ID: <20060713170127.GI12807@redhat.com> (raw)
In-Reply-To: <20060713085808.GA9566@osiris.boeblingen.de.ibm.com>
On Thu, Jul 13, 2006 at 10:58:08AM +0200, Heiko Carstens wrote:
> Hi all,
>
> in include/asm-s390/bitops.h we have several typedefs:
>
> typedef struct { long _[__BITOPS_WORDS(size)]; } addrtype;
>
> sparse warns about these with "error: bad constant expression".
> Is there any way to tell sparse to be quiet? __force doesn't seem to work.
In many cases, these turn up as on-stack variables. It'd be
nice if sparse could figure out the maximum potential bound
and warn appropriately if they could reach $BIGSIZE.
For non-stack vars, it's less of an issue of course.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-07-13 17:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 8:58 sparse warnings for variable length arrays Heiko Carstens
2006-07-13 17:01 ` Dave Jones [this message]
2006-07-14 11:00 ` Martin Schwidefsky
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=20060713170127.GI12807@redhat.com \
--to=davej@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/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