From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/5] fix qualifier dropping
Date: Wed, 18 Nov 2020 22:11:42 +0100 [thread overview]
Message-ID: <20201118211147.10680-1-luc.vanoostenryck@gmail.com> (raw)
This series fixes missing qualifier dropping in comma and
statement expressions and superfluous qualifier dropping in
increment or decrement expressions.
Luc Van Oostenryck (5):
unqual: add testcases
unqual: unqualify_type() should check for null ctypes
unqual: comma expressions should drop qualifiers
unqual: statement expressions should drop qualifiers
unqual: pre- & post-increment/decrement should *not* drop qualifiers
evaluate.c | 9 +++++----
validation/eval/unqual-comma.c | 12 ++++++++++++
validation/eval/unqual-postop.c | 22 ++++++++++++++++++++++
validation/eval/unqual-stmt-expr.c | 12 ++++++++++++
validation/eval/unqual02.c | 26 ++++++++++++++++++++++++++
5 files changed, 77 insertions(+), 4 deletions(-)
create mode 100644 validation/eval/unqual-comma.c
create mode 100644 validation/eval/unqual-postop.c
create mode 100644 validation/eval/unqual-stmt-expr.c
create mode 100644 validation/eval/unqual02.c
--
2.29.2
next reply other threads:[~2020-11-18 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 21:11 Luc Van Oostenryck [this message]
2020-11-18 21:11 ` [PATCH 1/5] unqual: add testcases Luc Van Oostenryck
2020-11-18 21:11 ` [PATCH 2/5] unqual: unqualify_type() should check for null ctypes Luc Van Oostenryck
2020-11-18 21:11 ` [PATCH 3/5] unqual: comma expressions should drop qualifiers Luc Van Oostenryck
2020-11-18 21:11 ` [PATCH 4/5] unqual: statement " Luc Van Oostenryck
2020-11-18 21:11 ` [PATCH 5/5] unqual: pre- & post-increment/decrement should *not* " 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=20201118211147.10680-1-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=torvalds@linux-foundation.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).