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/2] extend canonical order
Date: Wed, 12 Apr 2017 14:59:10 +0200 [thread overview]
Message-ID: <20170412125912.46641-1-luc.vanoostenryck@gmail.com> (raw)
After linearization, operands of binops of binops are
maintained in a 'canonical' order but this order is only:
anything > symbols > integer literals
but there is some value to impose a more complete order
as this creates more opportunities for CSE and help to
limit the number of patterns that need to be checked
at simplification of even during code generation.
This is what is done by this (almost single patch) series.
This series is available at:
git://github.com/lucvoo/sparse.git base-file
based on commit:
c9585071d02590f40175ea90c395d15ef70e9a1e (cset-setfval)
up to commit:
462a61a21b1e3bb17abce88fb1bdbc93d9653245
Luc Van Oostenryck (2):
CSE: split optim/cse-dual-compare.c in two files
CSE: extend canonical_order()
linearize.h | 4 +--
simplify.c | 29 +++++++++++-----
validation/call-inlined.c | 2 +-
.../optim/{cse-dual-compare.c => cse-dual-cmpeq.c} | 11 +-----
validation/optim/cse-dual-cmpne.c | 40 ++++++++++++++++++++++
5 files changed, 65 insertions(+), 21 deletions(-)
rename validation/optim/{cse-dual-compare.c => cse-dual-cmpeq.c} (68%)
create mode 100644 validation/optim/cse-dual-cmpne.c
--
2.12.0
next reply other threads:[~2017-04-12 13:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 12:59 Luc Van Oostenryck [this message]
2017-04-12 12:59 ` [PATCH 1/2] CSE: split optim/cse-dual-compare.c in two files Luc Van Oostenryck
2017-04-12 12:59 ` [PATCH 2/2] CSE: extend canonical_order() Luc Van Oostenryck
2017-04-12 13:08 ` [PATCH 0/2] extend canonical order 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=20170412125912.46641-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).