All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Li <sparse@chrisli.org>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [RFC] sparse SSA construction
Date: Wed, 16 Aug 2017 09:11:29 -0400	[thread overview]
Message-ID: <CANeU7Q=foyyU1_VvBKEdu8yLrOC2Si=2xboXYeokBBo0Bin64A@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxd1NrUevtuAJe4rOELKA5iOajxLo=MxHqpk6U82UtGvUw@mail.gmail.com>

On Wed, Aug 16, 2017 at 8:57 AM, Dibyendu Majumdar
<mobile@majumdar.org.uk> wrote:
>> Not sure I understand the question.
>
> I meant that it would nice to save a function like SSA(linear input)
> -> SSA output - because then you can rerun the SSA conversion several
> times during optimization.

OK, in that regard. I agree.
But it is not relative to the discussion we have there.
Before promoting memory variable to pseudo, it is still
valid SSA form.  After the prompting, we of course want
to stay in SSA.


>
> I think there is still an advantage as the implementation is bottom
> up, uses memoization / dynamic programming techniques, and hence might
> actually be quite efficient. I think Luc is better placed to comment
> on this.

May be. I haven't look at the code yet. The paper did not describe how
to play with "goto", so I don't no clue what Luc have to do to make the
goto work yet.

>
> But Luc's implementation handles gotos fine without the extra phase -
> hence please please try out the implementation before arriving at
> conclusions.

As I state very clear in the title, my thought as regarding the paper,
and paper only. I will take some time to read Luc's implementation
next.

I just want to get a confirm my thought on the paper is not too
far off. If I understand the paper incorrectly, it certainly will have negtive
impact on how I am going to read the code.

Thanks

Chris

  reply	other threads:[~2017-08-16 13:11 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
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 [this message]
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='CANeU7Q=foyyU1_VvBKEdu8yLrOC2Si=2xboXYeokBBo0Bin64A@mail.gmail.com' \
    --to=sparse@chrisli.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=mobile@majumdar.org.uk \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.