From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 06/10] attribute: factorize matching of '__attribute__'
Date: Sun, 9 Aug 2020 22:53:25 +0200 [thread overview]
Message-ID: <20200809205329.42811-7-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20200809205329.42811-1-luc.vanoostenryck@gmail.com>
Matching the keyword '__attribute__' (or '__attribute') needs
several tests and this matching is needed to handle attributes
or to skip them.
So, create an helper, match_attribute(), and use it in the loops
to handle and to skip attributes.
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
parse.c | 35 ++++++++++++++++-------------------
1 file changed, 16 insertions(+), 19 deletions(-)
diff --git a/parse.c b/parse.c
index 14b1746d38c5..681d98e49641 100644
--- a/parse.c
+++ b/parse.c
@@ -1761,6 +1761,20 @@ static struct token *handle_asm_name(struct token *token, struct decl_state *ctx
return token;
}
+///
+// test if @token is '__attribute__' (or one of its variant)
+static bool match_attribute(struct token *token)
+{
+ struct symbol *sym;
+
+ if (token_type(token) != TOKEN_IDENT)
+ return false;
+ sym = lookup_keyword(token->ident, NS_KEYWORD | NS_TYPEDEF);
+ if (!sym || sym->type != SYM_KEYWORD)
+ return false;
+ return sym->op->type & KW_ATTRIBUTE;
+}
+
static struct token *skip_attribute(struct token *token)
{
token = token->next;
@@ -1782,15 +1796,7 @@ static struct token *skip_attribute(struct token *token)
static struct token *skip_attributes(struct token *token)
{
- struct symbol *keyword;
- for (;;) {
- if (token_type(token) != TOKEN_IDENT)
- break;
- keyword = lookup_keyword(token->ident, NS_KEYWORD | NS_TYPEDEF);
- if (!keyword || keyword->type != SYM_KEYWORD)
- break;
- if (!(keyword->op->type & KW_ATTRIBUTE))
- break;
+ while (match_attribute(token)) {
token = expect(token->next, '(', "after attribute");
token = expect(token, '(', "after attribute");
while (token_type(token) == TOKEN_IDENT) {
@@ -1807,17 +1813,8 @@ static struct token *skip_attributes(struct token *token)
static struct token *handle_attributes(struct token *token, struct decl_state *ctx)
{
- struct symbol *keyword;
- for (;;) {
- if (token_type(token) != TOKEN_IDENT)
- break;
- keyword = lookup_keyword(token->ident, NS_KEYWORD | NS_TYPEDEF);
- if (!keyword || keyword->type != SYM_KEYWORD)
- break;
- if (!(keyword->op->type & KW_ATTRIBUTE))
- break;
+ while (match_attribute(token))
token = attribute_specifier(token->next, ctx);
- }
return token;
}
--
2.28.0
next prev parent reply other threads:[~2020-08-09 20:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-09 20:53 [PATCH 00/10] separate parsing of asm-names from attributes Luc Van Oostenryck
2020-08-09 20:53 ` [PATCH 01/10] use lookup_keyword() for qualifiers Luc Van Oostenryck
2020-08-09 20:53 ` [PATCH 02/10] attribute: split handle_asm_name() from handle_attributes() Luc Van Oostenryck
2020-08-09 20:53 ` [PATCH 03/10] attribute: fold parse_asm_declarator() into handle_asm_name() Luc Van Oostenryck
2020-08-09 20:53 ` [PATCH 04/10] attribute: remove argument 'keywords' from handle_attributes() Luc Van Oostenryck
2020-08-09 20:53 ` [PATCH 05/10] attribute: directly use attribute_specifier() to handle attributes Luc Van Oostenryck
2020-08-09 20:53 ` Luc Van Oostenryck [this message]
2020-08-09 20:53 ` [PATCH 07/10] attribute: no need to lookup '__attribute__' in NS_KEYWORD Luc Van Oostenryck
2020-08-09 20:53 ` [PATCH 08/10] testing for SYM_KEYWORD is unneeded for lookup_keyword() Luc Van Oostenryck
2020-08-09 20:53 ` [PATCH 09/10] testing for sym->op " Luc Van Oostenryck
2020-08-09 20:53 ` [PATCH 10/10] keyword type is a bitmask and must be tested so 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=20200809205329.42811-7-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).