From: Alecs King <alecsk@gmail.com>
To: linux-sparse <linux-sparse@vger.kernel.org>
Subject: pre-process.c:569:18: error: bad constant expression
Date: Sat, 31 Dec 2005 15:30:06 +0800 [thread overview]
Message-ID: <20051231073006.GA3583@localhost> (raw)
int nargs = sym->arglist ? sym->arglist->count.normal : 0;
struct arg args[nargs];
gcc went fine but sparse complaint about this. Declaring such kind of
variable-sized arrays is allowed or not? Seems 'nargs' cannot be
evaluated until runtime..?
--
Alecs King
next reply other threads:[~2005-12-31 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-31 7:30 Alecs King [this message]
2005-12-31 19:31 ` pre-process.c:569:18: error: bad constant expression Linus Torvalds
2005-12-31 19:50 ` Linus Torvalds
2005-12-31 21:19 ` Linus Torvalds
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=20051231073006.GA3583@localhost \
--to=alecsk@gmail.com \
--cc=linux-sparse@vger.kernel.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