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] avoid creating orphaned OP_PHISRCs
Date: Thu, 13 Apr 2017 18:55:43 +0200 [thread overview]
Message-ID: <20170413165551.2785-1-luc.vanoostenryck@gmail.com> (raw)
The goal of this series is to avoid the creation of
orphaned OP_PHISRCs by simplify_loads() when it appears
that the loads con't be simplified afterall but that some
OP_PHISRC have already been created.
This change then lead to some code restructuration and
simplification.
This series is available at:
git://github.com/lucvoo/sparse.git fix-orphaned-phisrc
based on commits (a merge)
ac6c25bc066eab36942539ba11c7ab6cf0c63674 (bool-context)
ecda2093f19088fa94c3a4ac85359c6d0f1c64af (fix-cond-address)
fc981fe285c37ee297e93ef1cc8725caac75f9b3 (fix-bitfield-init-v2)
up to commit:
8b6716908788dfd1713215e7d4ddaa4f3d341948
Luc Van Oostenryck (8):
extract add_dominator() from find_dominating_parents()
add helper add_load_dominators()
remove test on initial phi->ident
avoid phisrc orphaned by simplify_loads()
avoid phisrc orphaned by find_dominating_stores()
integrate add_load_dominators() into rewrite_load_instruction()
check duplicated phi-nodes directly on dominators
avoid creating unneeded phi-sources
flow.c | 79 +++++++++++++++++++++++-------------
flow.h | 2 +-
memops.c | 14 ++-----
validation/linear/phisrc-orphan-ld.c | 22 ++++++++++
validation/linear/phisrc-orphan-st.c | 17 ++++++++
validation/loop-linearization.c | 30 +++++++-------
6 files changed, 110 insertions(+), 54 deletions(-)
create mode 100644 validation/linear/phisrc-orphan-ld.c
create mode 100644 validation/linear/phisrc-orphan-st.c
--
2.12.0
next reply other threads:[~2017-04-13 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 16:55 Luc Van Oostenryck [this message]
2017-04-13 16:55 ` [PATCH 1/8] extract add_dominator() from find_dominating_parents() Luc Van Oostenryck
2017-04-13 16:55 ` [PATCH 2/8] add helper add_load_dominators() Luc Van Oostenryck
2017-04-13 16:55 ` [PATCH 3/8] remove test on initial phi->ident Luc Van Oostenryck
2017-04-13 16:55 ` [PATCH 4/8] avoid phisrc orphaned by simplify_loads() Luc Van Oostenryck
2017-04-13 16:55 ` [PATCH 5/8] avoid phisrc orphaned by find_dominating_stores() Luc Van Oostenryck
2017-04-13 16:55 ` [PATCH 6/8] integrate add_load_dominators() into rewrite_load_instruction() Luc Van Oostenryck
2017-04-13 16:55 ` [PATCH 7/8] check duplicated phi-nodes directly on dominators Luc Van Oostenryck
2017-04-13 16:55 ` [PATCH 8/8] avoid creating unneeded phi-sources Luc Van Oostenryck
2017-05-18 17:04 ` [PATCH 0/8] avoid creating orphaned OP_PHISRCs 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=20170413165551.2785-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).