From: Arnd Bergmann <arnd@arndb.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] [SPARSE] increase MAXNEST constant
Date: Sat, 21 Jun 2003 13:53:43 +0200 [thread overview]
Message-ID: <200306211353.43512.arnd@arndb.de> (raw)
The MAXNEST constant in sparse is currently too small for
checking most of the kernel files. The deepest nesting
I found in the kernel is 25, so MAXNEST=32 should probably
be sufficient. It would be nice to check overruns here,
but I did not know where to best do it.
The problem is hidden when sparse is compiled with gcc-3.2
or earlier, but causes segmentation faults with gcc-3.3.
Arnd <><
===== pre-process.c 1.65 vs edited =====
--- 1.65/pre-process.c Wed Jun 11 01:03:25 2003
+++ edited/pre-process.c Sat Jun 21 13:26:03 2003
@@ -28,7 +28,7 @@
int verbose = 0;
int preprocessing = 0;
-#define MAXNEST (16)
+#define MAXNEST (32)
static int true_nesting = 0;
static int false_nesting = 0;
static struct token *unmatched_if = NULL;
next reply other threads:[~2003-06-21 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-21 11:53 Arnd Bergmann [this message]
2003-06-21 17:05 ` [PATCH] [SPARSE] increase MAXNEST constant 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=200306211353.43512.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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