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 1/8] kill uses of replaced instructions
Date: Thu, 17 Nov 2016 15:35:00 +0100 [thread overview]
Message-ID: <20161117143507.3598-2-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20161117143507.3598-1-luc.vanoostenryck@gmail.com>
When an instruction is replaced by a pseudo, the 'usage' of its
operands should be removed too but it's not the case.
The fix consists in calling kill_use() for each operands after
the pseudo is replaced.
Not all types of instruction are considered, only those which
can be replaced by a pseudo.
The following example illustrate the situation. When looking at
the output of test-linearize, the following function:
static int kill_add(int a, int b)
{
return (a + b) && 0;
}
without the patch, gives this output:
kill_add:
add.32 %r3 <- %arg1, %arg2
ret.32 $0
The 'add' instruction is obviously unneeded but nevertheless present.
Before any optimization the code was something like:
kill_add:
add.32 %r3 <- %arg1, %arg2
and_bool.32 %r4 <- %r3, $0
ret.32 %r4
During the simplification phase, the result of the 'and' instruction (%r4)
have been replaced by '0' and the instruction itself is discarded.
But '%r3' usage has not been adjusted and the further phases are not
aware that '%r3' is not needed anymore and so the 'add' instruction is kept
while not needed by anything.
With the patch the 'add' instruction is correctly discarded, giving the
expected output:
kill_add:
ret.32 $0
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
simplify.c | 20 +++++++++++++++
validation/kill-replaced-insn.c | 54 +++++++++++++++++++++++++++++++++++++++++
2 files changed, 74 insertions(+)
create mode 100644 validation/kill-replaced-insn.c
diff --git a/simplify.c b/simplify.c
index b5cd0ea7..85da5bec 100644
--- a/simplify.c
+++ b/simplify.c
@@ -253,6 +253,26 @@ static inline int constant(pseudo_t pseudo)
static int replace_with_pseudo(struct instruction *insn, pseudo_t pseudo)
{
convert_instruction_target(insn, pseudo);
+
+ switch (insn->opcode) {
+ case OP_SEL:
+ case OP_RANGE:
+ kill_use(&insn->src3);
+ case OP_BINARY ... OP_BINCMP_END:
+ kill_use(&insn->src2);
+ case OP_NOT:
+ case OP_NEG:
+ case OP_SYMADDR:
+ case OP_CAST:
+ case OP_SCAST:
+ case OP_FPCAST:
+ case OP_PTRCAST:
+ kill_use(&insn->src1);
+ break;
+
+ default:
+ assert(0);
+ }
insn->bb = NULL;
return REPEAT_CSE;
}
diff --git a/validation/kill-replaced-insn.c b/validation/kill-replaced-insn.c
new file mode 100644
index 00000000..be031b6c
--- /dev/null
+++ b/validation/kill-replaced-insn.c
@@ -0,0 +1,54 @@
+// See if the replaced operation is effectively killed or not
+
+static int kill_add(int a, int b)
+{
+ return (a + b) && 0;
+}
+
+static int kill_scast(short a)
+{
+ return ((int) a) && 0;
+}
+
+static int kill_ucast(unsigned char a)
+{
+ return ((int) a) && 0;
+}
+
+static int kill_pcast(int *a)
+{
+ return ((void*) a) && 0;
+}
+
+static int kill_fcast(double a)
+{
+ return ((int) a) && 0;
+}
+
+static int kill_select(int a)
+{
+ return (a ? 1 : 0) && 0;
+}
+
+static int kill_load(int *a)
+{
+ return *a && 0;
+}
+
+static int kill_store(int *a)
+{
+ return (*a = 1) && 0;
+}
+
+/*
+ * check-name: kill-replaced-insn
+ * check-command: test-linearize $file
+ *
+ * check-output-ignore
+ * check-output-excludes: add\\.
+ * check-output-excludes: scast\\.
+ * check-output-excludes: \\<cast\\.
+ * check-output-excludes: ptrcast\\.
+ * check-output-excludes: fpcast\\.
+ * check-output-excludes: sel\\.
+ */
--
2.10.2
next prev parent reply other threads:[~2016-11-17 18:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 14:34 [PATCH 0/8] fix uses of killed instructions Luc Van Oostenryck
2016-11-17 14:35 ` Luc Van Oostenryck [this message]
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-2-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).