From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: linux-sparse@vger.kernel.org
Subject: [GIT PULL] last pending patches for sparse's next release
Date: Fri, 12 May 2017 13:19:36 +0200 [thread overview]
Message-ID: <20170512111935.se6k5v2tlcwvtffc@desk.local> (raw)
Chris,
Please pull these patches for sparse's next release.
There is 3 fixes, plus Lance's support for _Static_assert
and the keyword cleanup that goes over it.
Regards,
Luc
--->8
The following changes since commit e35efe330c6ae7d154197c29b127560d569016d0:
Merge branches 'sent/float-expand-v2', 'sent/fix-kill-ttsb-v2', 'sent/fix-cond-address' and 'careful-concat-user-list' into tip (2017-04-30 02:08:54 +0200)
are available in the git repository at:
git://github.com/lucvoo/sparse.git tags/fixes-for-stable-20170512
for you to fetch changes up to 51de1cca1bde56d9a1c73142fa2c93eeba65d0bf:
Merge branches 'quiets-bool-cast-restricted-v2', 'keyword-cleanup-v2', 'not-so-crazy-v2' and 'ignore-void-if-convert-v3' into tip (2017-05-12 12:59:06 +0200)
----------------------------------------------------------------
Pending fixes for sparse's next release
----------------------------------------------------------------
Lance Richardson (1):
sparse: add support for _Static_assert
Luc Van Oostenryck (12):
avoid useless warning for 'bool <- restricted type' conversion
introduce REPEAT_CFG_CLEANUP
let kill_unreachable_bbs() clear REPEAT_CFG_CLEANUP
fix: kill unreachable BBs after killing a child
ignore VOID when trying to if-convert phi-nodes
keyword: add test case for reserved '_Static_assert'
keyword: regroup the [reserved] keywords
keyword: explicitly add C99 & C11 keywords
keyword: add more reserved keywords to the test case
keyword: add a comment about NS_TYPEDEF & reserved keywords
keyword: no pre-declaration needed for attribute names
Merge branches 'quiets-bool-cast-restricted-v2', 'keyword-cleanup-v2', 'not-so-crazy-v2' and 'ignore-void-if-convert-v3' into tip
evaluate.c | 6 ++
flow.c | 2 +
flow.h | 1 +
ident-list.h | 77 ++++-------------
linearize.c | 5 +-
parse.c | 46 +++++++++-
simplify.c | 41 +++++++--
validation/bool-cast-bad.c | 3 -
validation/bool-cast-implicit.c | 3 -
validation/bool-cast-restricted.c | 25 ++++++
validation/crazy02-not-so.c | 22 +++++
validation/optim/void-if-convert.c | 19 +++++
validation/reserved.c | 171 +++++++++++++++++++++++++++++++------
validation/static_assert.c | 71 +++++++++++++++
14 files changed, 392 insertions(+), 100 deletions(-)
create mode 100644 validation/bool-cast-restricted.c
create mode 100644 validation/crazy02-not-so.c
create mode 100644 validation/optim/void-if-convert.c
create mode 100644 validation/static_assert.c
next reply other threads:[~2017-05-12 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 11:19 Luc Van Oostenryck [this message]
2017-05-12 16:26 ` [GIT PULL] last pending patches for sparse's next release Ramsay Jones
2017-05-12 19:38 ` 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=20170512111935.se6k5v2tlcwvtffc@desk.local \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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