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/3] use internal size for __INT_MAX__ & friends
Date: Fri, 19 May 2017 13:20:50 +0200 [thread overview]
Message-ID: <20170519112053.24632-1-luc.vanoostenryck@gmail.com> (raw)
The goal of this series is to predefine macros like __INT_MAX__
with the same size of the one used by sparse while is used to be
size of the machine on which sparse was compiled.
Luc Van Oostenryck (3):
fix hardcoded size of wide chars
avoid to redefine __INT_MAX__ and friends
fix definition of __SCHAR_MAX__ & friends
char.c | 4 ++--
lib.c | 21 ++++++++++-----------
target.c | 2 ++
target.h | 2 ++
4 files changed, 16 insertions(+), 13 deletions(-)
--
2.13.0
next reply other threads:[~2017-05-19 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 11:20 Luc Van Oostenryck [this message]
2017-05-19 11:20 ` [PATCH 1/3] fix hardcoded size of wide chars Luc Van Oostenryck
2017-05-19 11:20 ` [PATCH 2/3] avoid to redefine __INT_MAX__ and friends Luc Van Oostenryck
2017-05-19 11:20 ` [PATCH 3/3] fix definition of __SCHAR_MAX__ & friends 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=20170519112053.24632-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).