linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 2/6] keyword: regroup the [reserved] keywords
Date: Fri,  5 May 2017 03:50:30 +0200	[thread overview]
Message-ID: <20170505015034.65164-3-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20170505015034.65164-1-luc.vanoostenryck@gmail.com>

The idents in "ident-list.h" are probably organized mainly
in the chronological order of their addition to the file and
as such a bit dispersed here and there.

Change this by regrouping them in Basic C/C99/C11/GCC extensions/...

Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
 ident-list.h | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/ident-list.h b/ident-list.h
index 3c7547783..dbed06858 100644
--- a/ident-list.h
+++ b/ident-list.h
@@ -16,7 +16,6 @@ IDENT_RESERVED(for);
 IDENT_RESERVED(while);
 IDENT_RESERVED(do);
 IDENT_RESERVED(goto);
-IDENT_RESERVED(_Static_assert);
 
 /* C typenames. They get marked as reserved when initialized */
 IDENT(struct);
@@ -26,13 +25,22 @@ IDENT(__attribute); IDENT(__attribute__);
 IDENT(volatile); IDENT(__volatile); IDENT(__volatile__);
 IDENT(double);
 
+/* C storage classes. They get marked as reserved when initialized */
+IDENT(static);
+
+/* C99 keywords */
+IDENT(restrict); IDENT(__restrict); IDENT(__restrict__);
+
+/* C11 keywords */
+IDENT_RESERVED(_Alignof);
+IDENT_RESERVED(_Static_assert);
+
 /* Special case for L'\t' */
 IDENT(L);
 
 /* Extended gcc identifiers */
 IDENT(asm); IDENT_RESERVED(__asm); IDENT_RESERVED(__asm__);
 IDENT(alignof); IDENT_RESERVED(__alignof); IDENT_RESERVED(__alignof__); 
-IDENT_RESERVED(_Alignof);
 IDENT_RESERVED(__sizeof_ptr__);
 IDENT_RESERVED(__builtin_types_compatible_p);
 IDENT_RESERVED(__builtin_offsetof);
@@ -88,12 +96,10 @@ IDENT(stdcall); IDENT(__stdcall__);
 IDENT(fastcall); IDENT(__fastcall__);
 IDENT(dllimport); IDENT(__dllimport__);
 IDENT(dllexport); IDENT(__dllexport__);
-IDENT(restrict); IDENT(__restrict); IDENT(__restrict__);
 IDENT(artificial); IDENT(__artificial__);
 IDENT(leaf); IDENT(__leaf__);
 IDENT(vector_size); IDENT(__vector_size__);
 IDENT(error); IDENT(__error__);
-IDENT(static);
 
 
 /* Preprocessor idents.  Direct use of __IDENT avoids mentioning the keyword
-- 
2.12.0


  parent reply	other threads:[~2017-05-05  1:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05  1:50 [PATCH 0/6] keyword cleanup Luc Van Oostenryck
2017-05-05  1:50 ` [PATCH 1/6] keyword: add test case for reserved '_Static_assert' Luc Van Oostenryck
2017-05-05  1:50 ` Luc Van Oostenryck [this message]
2017-05-05  1:50 ` [PATCH 3/6] keyword: explicitly add C99 & C11 keywords Luc Van Oostenryck
2017-05-05  1:50 ` [PATCH 4/6] keyword: add more reserved keywords to the test case Luc Van Oostenryck
2017-05-05  1:50 ` [PATCH 5/6] keyword: add a comment about NS_TYPEDEF & reserved keywords Luc Van Oostenryck
2017-05-05  1:50 ` [PATCH 6/6] keyword: no pre-declaration needed for attribute names Luc Van Oostenryck
2017-05-07  5:15 ` [PATCH 0/6] keyword cleanup Christopher Li

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=20170505015034.65164-3-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).