From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [GIT PULL] llvm fixes
Date: Sun, 5 Nov 2017 18:03:52 +0100 [thread overview]
Message-ID: <20171105170349.o7r7z3qb4a36pmtf@ltop.local> (raw)
In-Reply-To: <CANeU7Qk4AGhSzzpPXT1-NmWRzSprUXEjWm6o1iy8yKAb-TceQg@mail.gmail.com>
On Sun, Nov 05, 2017 at 04:49:37PM +0800, Christopher Li wrote:
> >commit 5674da2d1af2467605fcc9b798fb54ee2d28efc7
> >Author: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
> >Date: Mon Mar 20 15:18:53 2017 +0100
> >
> > canonicalize compare instructions
> >
> > Currently only commutative instructions are canonicalized
> > (the "simpler" operands, often a constant, is forced, if present
> > to be in the second operand). This improve CSE (more cases are
> > considered as equivalent) and help to reduce the number of "pattern"
> > to be handled at simplification.
> >
>
>
> Notice that LT and GT and equivalent instructions after swapping the src.
> Another way to do it we might just remove one kind of instruction from the
> sparse IR. From the linearization point just map GT into LT and swap the source.
>
> So the IR does not allow those duplicated equilateral instructions. There is
> less canonization to be done.
The principal and most important action done during canonicalization is
insuring that constants are on the RHS.
-- Luc
next prev parent reply other threads:[~2017-11-05 17:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 9:51 [GIT PULL] llvm fixes Luc Van Oostenryck
2017-10-02 19:49 ` Luc Van Oostenryck
2017-10-16 14:41 ` Luc Van Oostenryck
2017-10-29 23:13 ` Christopher Li
2017-11-05 8:29 ` Christopher Li
2017-11-05 17:10 ` Luc Van Oostenryck
2017-11-05 23:18 ` Christopher Li
2017-11-12 1:04 ` Christopher Li
2017-11-12 5:05 ` Luc Van Oostenryck
2017-11-12 10:10 ` Christopher Li
2017-11-12 5:45 ` Luc Van Oostenryck
2017-11-05 8:49 ` Christopher Li
2017-11-05 17:03 ` Luc Van Oostenryck [this message]
2017-10-29 23:31 ` Christopher Li
2017-10-30 6:14 ` Luc Van Oostenryck
2017-11-17 9:51 ` Luc Van Oostenryck
[not found] ` <CANeU7QnTtcKP9ukNqGmMzfVMviYwYEfYFhgLRHHGxCqR7sPGEQ@mail.gmail.com>
2017-11-17 19:50 ` Luc Van Oostenryck
2017-11-26 17:42 ` Christopher Li
2017-11-26 19:34 ` 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=20171105170349.o7r7z3qb4a36pmtf@ltop.local \
--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).