From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/5] Fixes for generic selection
Date: Fri, 19 Jun 2020 17:02:55 +0200 [thread overview]
Message-ID: <20200619150300.63695-1-luc.vanoostenryck@gmail.com> (raw)
This series contains:
* the controlling expression must be lvalue-converted,
array-to-pointer & function-to-pointer converted.
These are the rules following the resolution of DR481
and are also used for C17 (and are followed by both
GCC & clang).
* validate the type of the associations.
These patches are available for testing & review at:
git://git.kernel.org/pub/scm/devel/sparse/sparse.git fix-gensel
Note: A small inconsistency remains: a plain char
will match a signed char or a unsigned char.
Luc Van Oostenryck (5):
gensel: add testcases from DR481
gensel: use temporary variable in generic selection
gensel: controlling expression must be lvalue converted
gensel: controlling expression must be pointer-converted
gensel: validate the type of the associations
evaluate.c | 33 ++++++++++++++++++++++++++++++---
validation/generic-dr481.c | 17 +++++++++++++++++
2 files changed, 47 insertions(+), 3 deletions(-)
create mode 100644 validation/generic-dr481.c
--
2.27.0
next reply other threads:[~2020-06-19 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 15:02 Luc Van Oostenryck [this message]
2020-06-19 15:02 ` [PATCH 1/5] gensel: add testcases from DR481 Luc Van Oostenryck
2020-06-19 15:02 ` [PATCH 2/5] gensel: use temporary variable in generic selection Luc Van Oostenryck
2020-06-19 15:02 ` [PATCH 3/5] gensel: controlling expression must be lvalue converted Luc Van Oostenryck
2020-06-19 15:02 ` [PATCH 4/5] gensel: controlling expression must be pointer-converted Luc Van Oostenryck
2020-06-19 15:03 ` [PATCH 5/5] gensel: validate the type of the associations 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=20200619150300.63695-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).