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 0/6] modifiers inheritance by '&' and 'typeof()'
Date: Thu, 24 Nov 2016 18:09:41 +0100 [thread overview]
Message-ID: <20161124170947.14379-1-luc.vanoostenryck@gmail.com> (raw)
There is several issues regarding which modifiers is or must be
preserved when using the '&' or 'typeof()' operators. There is
also no explicit tests for these. This serie aims to improve this
situation by:
- avoid to inherit storage modifiers by '&' (patch 1)
- simplify an existing test (patch 2 & 3)
- create a bunch of test cases (patch 4 & 5)
- partial fix for modifiers needing to be inherited by typeof
(patch 6)
The last patch is marked as '[RFC]' because it needs some clarification
on the wanted semantics of some modifiers in some situations.
In particular, MOD_NODEREF & MOD_SAFE are for the moment not addressed,
like the address space.
Lastly, especially for what concerns MOD_SAFE, some others changes are
needed.
Luc Van Oostenryck (6):
storage should not be inherited by pointers
testsuite: simplify test function-pointer-inheritance
use a shorter name for function-pointer-modifier-inheritance.c
testsuite: test modifiers preserved by '&' operator
testsuite: test modifiers preserved by 'typeof()'
[RFC] some modifiers need to be preserved by 'typeof()'
symbol.c | 8 +-
symbol.h | 4 +-
validation/function-pointer-inheritance.c | 9 ++
validation/function-pointer-modifier-inheritance.c | 18 ----
validation/nocast.c | 2 +-
validation/ptr-inherit.c | 80 +++++++++++++++
validation/typeof-addresspace.c | 20 ++++
validation/typeof-mods.c | 109 +++++++++++++++++++++
validation/typeof-noderef.c | 19 ++++
validation/typeof-safe.c | 23 +++++
10 files changed, 270 insertions(+), 22 deletions(-)
create mode 100644 validation/function-pointer-inheritance.c
delete mode 100644 validation/function-pointer-modifier-inheritance.c
create mode 100644 validation/ptr-inherit.c
create mode 100644 validation/typeof-addresspace.c
create mode 100644 validation/typeof-mods.c
create mode 100644 validation/typeof-noderef.c
create mode 100644 validation/typeof-safe.c
--
2.10.2
next reply other threads:[~2016-11-24 17:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 17:09 Luc Van Oostenryck [this message]
2016-11-24 17:09 ` [PATCH 1/6] storage should not be inherited by pointers Luc Van Oostenryck
2016-11-25 2:09 ` Christopher Li
2016-11-25 3:38 ` Luc Van Oostenryck
2016-11-28 1:04 ` Christopher Li
2016-11-28 2:02 ` Luc Van Oostenryck
2016-11-24 17:09 ` [PATCH 2/6] testsuite: simplify test function-pointer-inheritance Luc Van Oostenryck
2016-11-24 17:09 ` [PATCH 3/6] use a shorter name for function-pointer-modifier-inheritance.c Luc Van Oostenryck
2016-11-24 17:09 ` [PATCH 4/6] testsuite: test modifiers preserved by '&' operator Luc Van Oostenryck
2016-11-24 17:09 ` [PATCH 5/6] testsuite: test modifiers preserved by 'typeof()' Luc Van Oostenryck
2016-11-24 17:09 ` [PATCH 6/6] [RFC] some modifiers need to be " 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=20161124170947.14379-1-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).