From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Stephen Boyd <sboyd@codeaurora.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Christopher Li <sparse@chrisli.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/3] diagnose unknown escapes after preprocessing
Date: Tue, 7 Feb 2017 18:45:04 +0100 [thread overview]
Message-ID: <20170207174507.22722-1-luc.vanoostenryck@gmail.com> (raw)
This series aims to solve the wrong warning recently
received when using sparse on Linux's kernel for arm64.
It quite straightforwardly move the diagnostic of
unknown escape sequence together with escape conversion,
after preprocessing.
Patch 1 is just a test case (and could be folded with patch 2)
Patch 2 is the fix in itself
Patch 3 remove potential cruft left by patch 2.
Luc Van Oostenryck (3):
add testcase for wrong early escape conversion
warn on unknown escapes after preprocessing
remove 'Escape' from token character class
char.c | 6 ++++++
tokenize.c | 28 +++++++++++-----------------
validation/escapes.c | 2 +-
validation/preprocessor/early-escape.c | 22 ++++++++++++++++++++++
4 files changed, 40 insertions(+), 18 deletions(-)
create mode 100644 validation/preprocessor/early-escape.c
--
2.11.0
next reply other threads:[~2017-02-07 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 17:45 Luc Van Oostenryck [this message]
2017-02-07 17:45 ` [PATCH 1/3] add testcase for wrong early escape conversion Luc Van Oostenryck
2017-02-07 17:45 ` [PATCH 2/3] warn on unknown escapes after preprocessing Luc Van Oostenryck
2017-02-07 17:45 ` [PATCH 3/3] remove 'Escape' from token character class Luc Van Oostenryck
2017-02-07 18:50 ` [PATCH 0/3] diagnose unknown escapes after preprocessing Christopher Li
2017-02-07 20:10 ` Stephen Boyd
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=20170207174507.22722-1-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sboyd@codeaurora.org \
--cc=sparse@chrisli.org \
--cc=viro@zeniv.linux.org.uk \
/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).