From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Ben Dooks <ben.dooks@codethink.co.uk>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/3] add some builtin types for printf format checking
Date: Sun, 4 Oct 2020 13:43:46 +0200 [thread overview]
Message-ID: <20201004114349.81440-1-luc.vanoostenryck@gmail.com> (raw)
The checking of printf format strings needs a few more builtin types.
For example, a type for wide string is needed for "%Ls" and more are
needed to support "%n" with the different possible lenght modifiers.
Luc Van Oostenryck (3):
add builtin type for wide strings
add builtin types for signed char* and short *
add builtin types for size_t*, intmax_t* & ptrdiff_t*
symbol.c | 19 +++++++++++++++++++
symbol.h | 3 +++
2 files changed, 22 insertions(+)
--
2.28.0
next reply other threads:[~2020-10-04 11:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-04 11:43 Luc Van Oostenryck [this message]
2020-10-04 11:43 ` [PATCH 1/3] add builtin type for wide strings Luc Van Oostenryck
2020-10-04 11:43 ` [PATCH 2/3] add builtin types for signed char* and short * Luc Van Oostenryck
2020-10-04 11:43 ` [PATCH 3/3] add builtin types for size_t*, intmax_t* & ptrdiff_t* 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=20201004114349.81440-1-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=ben.dooks@codethink.co.uk \
--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).