From: Christopher Li <sparse@chrisli.org>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [RFC] sparse SSA construction
Date: Tue, 15 Aug 2017 09:59:30 -0400 [thread overview]
Message-ID: <CANeU7Qk9C-78+-a2TOGUWiLof9S_p9vO6bHyNf6xZqZ5X1CoUQ@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxchKzgv_cN7MzZnT09OX1thdODoinqSVzK8jSxdPCVK8w@mail.gmail.com>
On Tue, Aug 15, 2017 at 9:41 AM, Dibyendu Majumdar
<mobile@majumdar.org.uk> wrote:
>> I don't feel it's needed to patchbomb the ML for the moment
>> so I'll only give the URL to the repo:
>>
>> git://github.com/lucvoo/sparse.git sssa
>
> I have merged the new SSA implementation in your sssa-mini-clean
> branch - which I understand is minimal set of changes needed for the
> new SSA on top of RC5 - into my project dmrC.
>
> I have been testing the changes - and so far I am pleased to report
> that after a small set of changes (described below) - all my existing
> tests pass.
>
Thanks for the report and testing.
> a) I had to disallow struct / union types from being treated as simple types.
> b) I am setting UNDEF pseudos a value of 0 in LLVM backend - this is
> to ensure I can do the same in other backends.
> c) I found that CBR instructions can get a PSEUDO_VAL as the condition
> which was not being handled correctly in my version of LLVM backend.
> Somehow this did not occur in the past so I am not yet sure how this
> is related to the changes.
>
> The new implementation does not appear to suffer from the performance
> degradation we saw after removing the single store shortcut.
That is good to hear. With the shortcut removed, sparse actually suffer
a lot of finding store/load domination for large graphs. The recursive
way of finding domination has no cache acceleration at all.
There is a lot of room to improvement.
>
> Finally the new code seems simpler and elegant. I would suggest adding
> some comments in ssa.c - perhaps copy the pseudo code from the paper
> it is based on - to better explain what is going on.
Yes, I think that is helpful. I am reading the paper right now.
This ssa conversion will need to break into smaller piece for review
and merge. The general recommended number of patch for the first
round is 15 or so at a time in the Linux kernel submmitting-patches.rst
documentation.
Chris
next prev parent reply other threads:[~2017-08-15 13:59 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 20:26 [RFC] sparse SSA construction Luc Van Oostenryck
2017-08-06 23:01 ` Christopher Li
2017-08-06 23:44 ` Luc Van Oostenryck
2017-08-07 0:33 ` Christopher Li
2017-08-07 1:21 ` Luc Van Oostenryck
2017-08-07 1:44 ` Christopher Li
2017-08-15 13:41 ` Dibyendu Majumdar
2017-08-15 13:59 ` Christopher Li [this message]
2017-08-15 14:06 ` Dibyendu Majumdar
2017-08-15 14:07 ` Christopher Li
2017-08-15 14:09 ` Dibyendu Majumdar
2017-08-15 14:18 ` Christopher Li
2017-08-15 18:36 ` Linus Torvalds
2017-08-15 20:14 ` Luc Van Oostenryck
2017-08-15 20:43 ` Linus Torvalds
2017-08-15 21:43 ` Luc Van Oostenryck
2017-08-15 22:44 ` Dibyendu Majumdar
2017-08-16 5:36 ` Christopher Li
2017-08-16 5:15 ` Christopher Li
2017-08-16 4:23 ` Christopher Li
2017-08-16 4:58 ` Christopher Li
2017-08-16 10:40 ` Dibyendu Majumdar
2017-08-16 13:17 ` Christopher Li
2017-08-16 6:41 ` Luc Van Oostenryck
2017-08-16 11:02 ` Dibyendu Majumdar
2017-08-16 12:00 ` Luc Van Oostenryck
2017-08-16 12:16 ` Dibyendu Majumdar
2017-08-16 12:23 ` Christopher Li
2017-08-16 12:28 ` Luc Van Oostenryck
2017-08-16 12:39 ` Dibyendu Majumdar
2017-08-16 12:50 ` Christopher Li
2017-08-16 12:57 ` Dibyendu Majumdar
2017-08-16 13:11 ` Christopher Li
2017-08-16 13:22 ` Christopher Li
2017-08-16 12:17 ` Christopher Li
2017-08-15 20:37 ` 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=CANeU7Qk9C-78+-a2TOGUWiLof9S_p9vO6bHyNf6xZqZ5X1CoUQ@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=mobile@majumdar.org.uk \
/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).