From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 2/5] C11: teach sparse about '_Noreturn'
Date: Thu, 5 Jan 2017 04:22:17 +0100 [thread overview]
Message-ID: <20170105032220.7339-3-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20170105032220.7339-1-luc.vanoostenryck@gmail.com>
This is mainly a new name for GCC's 'noreturn' attribute but defined
as a new function specifier.
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
parse.c | 14 ++++++++++++++
validation/c11-noreturn.c | 9 +++++++++
2 files changed, 23 insertions(+)
create mode 100644 validation/c11-noreturn.c
diff --git a/parse.c b/parse.c
index 7fc145db..f131d0e6 100644
--- a/parse.c
+++ b/parse.c
@@ -122,6 +122,12 @@ static struct symbol_op inline_op = {
.declarator = inline_specifier,
};
+static declarator_t noreturn_specifier;
+static struct symbol_op noreturn_op = {
+ .type = KW_MODIFIER,
+ .declarator = noreturn_specifier,
+};
+
static struct symbol_op auto_op = {
.type = KW_MODIFIER,
.declarator = auto_specifier,
@@ -432,6 +438,8 @@ static struct init_keyword {
{ "__inline", NS_TYPEDEF, .op = &inline_op },
{ "__inline__", NS_TYPEDEF, .op = &inline_op },
+ { "_Noreturn", NS_TYPEDEF, .op = &noreturn_op },
+
/* Ignored for now.. */
{ "restrict", NS_TYPEDEF, .op = &restrict_op},
{ "__restrict", NS_TYPEDEF, .op = &restrict_op},
@@ -1368,6 +1376,12 @@ static struct token *inline_specifier(struct token *next, struct decl_state *ctx
return next;
}
+static struct token *noreturn_specifier(struct token *next, struct decl_state *ctx)
+{
+ apply_qualifier(&next->pos, &ctx->ctype, MOD_NORETURN);
+ return next;
+}
+
static struct token *const_qualifier(struct token *next, struct decl_state *ctx)
{
apply_qualifier(&next->pos, &ctx->ctype, MOD_CONST);
diff --git a/validation/c11-noreturn.c b/validation/c11-noreturn.c
new file mode 100644
index 00000000..bc20de82
--- /dev/null
+++ b/validation/c11-noreturn.c
@@ -0,0 +1,9 @@
+static _Noreturn void foo(void) { while (1) ; }
+
+/*
+ * check-name: c11-noreturn
+ * check-command: test-parsing -std=c11 $file
+ *
+ * check-output-ignore
+ * check-output-contains: \[noreturn\]
+ */
--
2.11.0
next prev parent reply other threads:[~2017-01-05 3:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 3:22 [PATCH 0/5] add basic support for C11 Luc Van Oostenryck
2017-01-05 3:22 ` [PATCH 1/5] C11: teach sparse about '_Thread_local' Luc Van Oostenryck
2017-01-05 3:22 ` Luc Van Oostenryck [this message]
2017-01-05 3:22 ` [PATCH 3/5] C11: teach sparse about '_Alignof()' Luc Van Oostenryck
2017-01-05 3:22 ` [PATCH 4/5] C11: teach sparse about '_Alignas()' Luc Van Oostenryck
2017-01-05 3:22 ` [PATCH 5/5] C11: teach sparse about '--std={c11,gnu11}' Luc Van Oostenryck
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=20170105032220.7339-3-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@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;
as well as URLs for NNTP newsgroup(s).