From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Christopher Li <sparse@chrisli.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/8] fix uses of killed instructions
Date: Thu, 17 Nov 2016 15:34:59 +0100 [thread overview]
Message-ID: <20161117143507.3598-1-luc.vanoostenryck@gmail.com> (raw)
The series fixes some issues regarding the operands of killed
instructions not having their usage adjusted.
The main apparent consequence of this situation is that
some instructions which should be considered as unneeded are
not removed from the code as expected. This can sometimes have
a cascading effect that can be "quite interesting".
There is some closely related issues that remains,
for example the situation of the exotic instructions.
It's also possible that something is missing with OP_SYMADDR.
OP_LOAD, OP_STORE & OP_CALL are completly ignored and their
correct handling need another approach, so they're also
ignored by this series.
*ATTENTION*
The test cases in this series depends on some
features I added to the test-suite that I posted the
10th November with the "fix discarded label statement" serie.
Luc Van Oostenryck (8):
kill uses of replaced instructions
fix killing OP_SETVAL instructions
fix killing OP_PHI instructions
fix killing OP_CAST & friends
fix killing OP_SELECT
fix killing OP_COMPUTEDGOTO
explicitely ignore killing OP_ENTRY
cleanup kill_instruction()
simplify.c | 74 ++++++++++++++++++++++++++++-------------
validation/kill-casts.c | 22 ++++++++++++
validation/kill-computedgoto.c | 17 ++++++++++
validation/kill-phi-node.c | 18 ++++++++++
validation/kill-replaced-insn.c | 61 +++++++++++++++++++++++++++++++++
validation/kill-select.c | 16 +++++++++
6 files changed, 184 insertions(+), 24 deletions(-)
create mode 100644 validation/kill-casts.c
create mode 100644 validation/kill-computedgoto.c
create mode 100644 validation/kill-phi-node.c
create mode 100644 validation/kill-replaced-insn.c
create mode 100644 validation/kill-select.c
--
next reply other threads:[~2016-11-17 17:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 14:34 Luc Van Oostenryck [this message]
2016-11-17 14:35 ` [PATCH 1/8] kill uses of replaced instructions Luc Van Oostenryck
2016-11-17 14:35 ` [PATCH 2/8] fix killing OP_SETVAL instructions Luc Van Oostenryck
2016-11-17 14:35 ` [PATCH 3/8] fix killing OP_PHI instructions Luc Van Oostenryck
2016-11-17 14:35 ` [PATCH 4/8] fix killing OP_CAST & friends Luc Van Oostenryck
2016-11-17 14:35 ` [PATCH 5/8] fix killing OP_SELECT Luc Van Oostenryck
2016-11-17 14:35 ` [PATCH 6/8] fix killing OP_COMPUTEDGOTO Luc Van Oostenryck
2016-11-17 14:35 ` [PATCH 7/8] explicitely ignore killing OP_ENTRY Luc Van Oostenryck
2016-11-17 14:35 ` [PATCH 8/8] cleanup kill_instruction() 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=20161117143507.3598-1-luc.vanoostenryck@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).