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 3/8] fix killing OP_PHI instructions
Date: Thu, 17 Nov 2016 15:35:02 +0100 [thread overview]
Message-ID: <20161117143507.3598-4-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20161117143507.3598-1-luc.vanoostenryck@gmail.com>
Currently kill_instruction() doesn't do anything with the
sources of OP_PHI instructions. But when these instructions
are removed the 'usage' of the associated sources must also
be removed. This is not done and as result the instructions
producing the phi-sources are not optimized away as expected.
This patch fixes that by calling clear_phi() when killing a
phi-instruction.
For example, when looking at the output of test-linearize,
the following function:
void foo(int a, int *b, unsigned int g);
void foo(int a, int *b, unsigned int g)
{
int d = 0;
if ((!a || *b) && g)
d = 16;
else
d = 8;
}
gives this output without the patch:
foo:
br %arg1, .L1, .L2
.L1:
phisrc.32 %phi1 <- $1
br .L3
.L2:
load.32 %r3 <- 0[%arg2]
phisrc.32 %phi2 <- %r3
br .L3
.L3:
ret
The 'phisrc' instructions are obviously unneeded but nevertheless present.
With the patch, the output is much closer to what's expected:
foo:
br %arg1, .L3, .L2
.L2:
load.32 %r3 <- 0[%arg2]
br .L3
.L3:
ret
Note 1) The 'load' instruction is also dead and should have been removed
but it's separate problem.
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
simplify.c | 1 +
validation/kill-phi-node.c | 18 ++++++++++++++++++
2 files changed, 19 insertions(+)
create mode 100644 validation/kill-phi-node.c
diff --git a/simplify.c b/simplify.c
index d07ca1b1..421b28f2 100644
--- a/simplify.c
+++ b/simplify.c
@@ -203,6 +203,7 @@ void kill_instruction(struct instruction *insn)
return;
case OP_PHI:
+ clear_phi(insn);
insn->bb = NULL;
repeat_phase |= REPEAT_CSE;
return;
diff --git a/validation/kill-phi-node.c b/validation/kill-phi-node.c
new file mode 100644
index 00000000..88de9f96
--- /dev/null
+++ b/validation/kill-phi-node.c
@@ -0,0 +1,18 @@
+void foo(int a, int *b, unsigned int g);
+void foo(int a, int *b, unsigned int g)
+{
+ int d = 0;
+
+ if ((!a || *b) && g)
+ d = 16;
+ else
+ d = 8;
+}
+
+/*
+ * check-name: kill-phi-node
+ * check-command: test-linearize $file
+ *
+ * check-output-ignore
+ * check-output-excludes: phisrc\\.
+ */
--
2.10.2
next prev parent reply other threads:[~2016-11-17 18:44 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 ` [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 ` Luc Van Oostenryck [this message]
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-4-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).