From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Christopher Li <sparse@chrisli.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 5/5] check the storage of C99 for-loop initializers
Date: Sat, 18 Feb 2017 21:30:48 +0100 [thread overview]
Message-ID: <20170218203048.22276-6-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20170218203048.22276-1-luc.vanoostenryck@gmail.com>
In C99, it is valid to declarare a variable inside
a for-loop initializer but only when the storage is local
(automatic or register).
Until now this was not enforced.
Fix that by adding the appropriate checks called by
external_declaration() via the new function pointer when
parsing this declaration in a for-loop context.
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
parse.c | 17 ++++++++++++++++-
validation/c99-for-loop-decl.c | 1 -
2 files changed, 16 insertions(+), 2 deletions(-)
diff --git a/parse.c b/parse.c
index 866186fd2..5b029ccdc 100644
--- a/parse.c
+++ b/parse.c
@@ -2217,6 +2217,21 @@ static struct token *parse_return_statement(struct token *token, struct statemen
return expression_statement(token->next, &stmt->ret_value);
}
+static void add_for_loop_decl(struct symbol_list **list, struct symbol *sym)
+{
+ unsigned long storage;
+
+ storage = sym->ctype.modifiers & MOD_STORAGE;
+ if (storage & ~(MOD_AUTO | MOD_REGISTER)) {
+ const char *name = show_ident(sym->ident);
+ sparse_error(sym->pos, "non-local var '%s' in for-loop initializer", name);
+ sym->ctype.modifiers &= ~MOD_STORAGE;
+ }
+
+ add_symbol(list, sym);
+ fn_local_symbol(sym);
+}
+
static struct token *parse_for_statement(struct token *token, struct statement *stmt)
{
struct symbol_list *syms;
@@ -2230,7 +2245,7 @@ static struct token *parse_for_statement(struct token *token, struct statement *
e1 = NULL;
/* C99 variable declaration? */
if (lookup_type(token)) {
- token = external_declaration(token, NULL, &syms);
+ token = external_declaration(token, add_for_loop_decl, &syms);
} else {
token = parse_expression(token, &e1);
token = expect(token, ';', "in 'for'");
diff --git a/validation/c99-for-loop-decl.c b/validation/c99-for-loop-decl.c
index b9db8c9c6..e813b0ae3 100644
--- a/validation/c99-for-loop-decl.c
+++ b/validation/c99-for-loop-decl.c
@@ -30,7 +30,6 @@ static int c99(void)
/*
* check-name: C99 for-loop declarations
- * check-known-to-fail
*
* check-error-start
c99-for-loop-decl.c:22:27: warning: symbol with external linkage has initializer
--
2.11.0
prev parent reply other threads:[~2017-02-18 20:31 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-18 20:30 [PATCH 0/5] more validation of C99 for-loop initializers Luc Van Oostenryck
2017-02-18 20:30 ` [PATCH 1/5] replace test for c99 " Luc Van Oostenryck
2017-02-18 22:37 ` Ramsay Jones
2017-02-19 1:10 ` Luc Van Oostenryck
2017-02-19 20:58 ` Ramsay Jones
2017-02-20 7:20 ` [PATCH v2 0/5] more validation of C99 " Luc Van Oostenryck
2017-02-20 7:20 ` [PATCH v2 1/5] replace test for c99 " Luc Van Oostenryck
2017-02-20 14:05 ` Ramsay Jones
2017-02-20 7:20 ` [PATCH v2 2/5] add test case for scope of C99 for-loop declarations Luc Van Oostenryck
2017-02-20 7:20 ` [PATCH v2 3/5] add test cases for storage of c99 " Luc Van Oostenryck
2017-02-20 7:20 ` [PATCH v2 4/5] add a method to external_declaration() Luc Van Oostenryck
2017-02-20 7:20 ` [PATCH v2 5/5] check the storage of C99 for-loop initializers Luc Van Oostenryck
2017-02-18 20:30 ` [PATCH 2/5] add test case for scope of C99 for-loop declarations Luc Van Oostenryck
2017-02-18 20:30 ` [PATCH 3/5] add test cases for storage of c99 " Luc Van Oostenryck
2017-02-18 20:30 ` [PATCH 4/5] add a method to external_declaration() Luc Van Oostenryck
2017-02-27 15:37 ` Christopher Li
2017-02-27 21:34 ` Luc Van Oostenryck
2017-02-28 9:46 ` Luc Van Oostenryck
2017-02-28 10:03 ` [PATCH v3 0/7] more validation of C99 for-loop initializers Luc Van Oostenryck
2017-02-28 10:03 ` [PATCH v3 1/7] replace test for c99 " Luc Van Oostenryck
2017-02-28 10:03 ` [PATCH v3 2/7] add test case for scope of C99 for-loop declarations Luc Van Oostenryck
2017-02-28 10:03 ` [PATCH v3 3/7] add test cases for storage of c99 " Luc Van Oostenryck
2017-02-28 10:04 ` [PATCH v3 4/7] add a method to external_declaration() Luc Van Oostenryck
2017-03-05 14:04 ` Christopher Li
2017-03-05 15:12 ` Luc Van Oostenryck
2017-03-06 1:13 ` Christopher Li
2017-03-05 19:21 ` [PATCH v4 0/6] more validation of C99 for-loop initializers Luc Van Oostenryck
2017-03-05 19:21 ` [PATCH v4 1/6] replace test for c99 " Luc Van Oostenryck
2017-03-05 19:21 ` [PATCH v4 2/6] add test case for scope of C99 for-loop declarations Luc Van Oostenryck
2017-03-05 19:21 ` [PATCH v4 3/6] add test cases for storage of c99 " Luc Van Oostenryck
2017-03-05 19:21 ` [PATCH v4 4/6] add an optional validation method to external_declaration() Luc Van Oostenryck
2017-03-05 19:21 ` [PATCH v4 5/6] check the storage of C99 for-loop initializers Luc Van Oostenryck
2017-03-05 19:21 ` [PATCH v4 6/6] move 'extern with initializer' validation after the validate method Luc Van Oostenryck
2017-03-06 0:59 ` [PATCH v4 0/6] more validation of C99 for-loop initializers Christopher Li
2017-03-06 1:08 ` Luc Van Oostenryck
2017-02-28 10:04 ` [PATCH v3 5/7] check the storage " Luc Van Oostenryck
2017-03-05 14:26 ` Christopher Li
2017-03-05 15:24 ` Luc Van Oostenryck
2017-02-28 10:04 ` [PATCH v3 6/7] make process_decl() aware of the presence of an initializer Luc Van Oostenryck
2017-03-05 14:49 ` Christopher Li
2017-03-05 15:29 ` Luc Van Oostenryck
2017-02-28 10:04 ` [PATCH v3 7/7] move check extern with initializer to default_process_decl() Luc Van Oostenryck
2017-02-28 16:34 ` [PATCH v3 0/7] more validation of C99 for-loop initializers Christopher Li
2017-02-28 16:40 ` Luc Van Oostenryck
2017-02-18 20:30 ` Luc Van Oostenryck [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=20170218203048.22276-6-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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;
as well as URLs for NNTP newsgroup(s).