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/2] predefine: fix multi-token predefine
Date: Sun, 5 Jul 2020 15:11:44 +0200 [thread overview]
Message-ID: <20200705131146.26439-1-luc.vanoostenryck@gmail.com> (raw)
The function predefine() and its variants are only valid
if they define a single-token value but predefine_min()
will produce a multi-token value if the type is signed.
This series contains a fix and a tescase for this.
Luc Van Oostenryck (2):
predefine: add testcase for multi-token predefines
predefine: fix multi-token predefine
predefine.c | 2 +-
validation/preprocessor/predef-token.c | 5 +++++
2 files changed, 6 insertions(+), 1 deletion(-)
create mode 100644 validation/preprocessor/predef-token.c
base-commit: 88c90bb192663bfc2dc54782c316e39e6fe26e1d
--
2.27.0
next reply other threads:[~2020-07-05 13:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 13:11 Luc Van Oostenryck [this message]
2020-07-05 13:11 ` [PATCH 1/2] predefine: add testcase for multi-token predefines Luc Van Oostenryck
2020-07-05 13:11 ` [PATCH 2/2] predefine: fix multi-token predefine 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=20200705131146.26439-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).