From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH v2 0/7] restricted pointers
Date: Wed, 8 Nov 2017 22:06:06 +0100 [thread overview]
Message-ID: <20171108210613.14252-1-luc.vanoostenryck@gmail.com> (raw)
The goal of this series is to prepare for a real support
for C99's 'restrict' type qualifier.
As preliminary steps this series also contains a
cleanup of the #define MOD_XYZ and as bonus it teaches
sparse about C11's '_Atomic' as type *qualifier*
Change since v1:
- remove patches related to error vs. warnings which
have already been integrated.
- improve commit messages
This series is available for review & testing at:
git://github.com/lucvoo/sparse.git restricted-pointers-v2
Luc Van Oostenryck (7):
remove never-used MOD_TYPEDEF
MOD_ACCESSED is not a type modifier ...
reorganize the definition of the modifiers
remove redundancy in MOD_STORAGE
define MOD_QUALIFIER for (MOD_CONST | MOD_VOLATILE)
associate MOD_RESTRICT with restrict-qualified variables
add support for C11's _Atomic as type qualifier
evaluate.c | 2 +-
expand.c | 2 +-
gdbhelpers | 12 +++---
ident-list.h | 2 +-
parse.c | 31 ++++++++++++---
show-parse.c | 4 +-
symbol.c | 4 +-
symbol.h | 80 ++++++++++++++++++-------------------
validation/c11-atomic.c | 93 ++++++++++++++++++++++++++++++++++++++++++++
validation/optim/restrict.c | 73 ++++++++++++++++++++++++++++++++++
validation/reload-aliasing.c | 41 +++++++++++++++++++
validation/restrict.c | 93 ++++++++++++++++++++++++++++++++++++++++++++
validation/typeof-mods.c | 28 +++++++++++++
13 files changed, 406 insertions(+), 59 deletions(-)
create mode 100644 validation/c11-atomic.c
create mode 100644 validation/optim/restrict.c
create mode 100644 validation/reload-aliasing.c
create mode 100644 validation/restrict.c
--
2.14.0
next reply other threads:[~2017-11-08 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 21:06 Luc Van Oostenryck [this message]
2017-11-08 21:06 ` [PATCH v2 1/7] remove never-used MOD_TYPEDEF Luc Van Oostenryck
2017-11-08 21:06 ` [PATCH v2 2/7] MOD_ACCESSED is not a type modifier Luc Van Oostenryck
2017-11-08 21:06 ` [PATCH v2 3/7] reorganize the definition of the modifiers Luc Van Oostenryck
2017-11-08 21:06 ` [PATCH v2 4/7] remove redundancy in MOD_STORAGE Luc Van Oostenryck
2017-11-08 21:06 ` [PATCH v2 5/7] define MOD_QUALIFIER for (MOD_CONST | MOD_VOLATILE) Luc Van Oostenryck
2017-11-08 21:06 ` [PATCH v2 6/7] associate MOD_RESTRICT with restrict-qualified variables Luc Van Oostenryck
2017-11-08 21:06 ` [PATCH v2 7/7] add support for C11's _Atomic as type qualifier Luc Van Oostenryck
2017-11-09 18:55 ` [PATCH v2 0/7] restricted pointers 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=20171108210613.14252-1-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).