linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: [RFC] sparse SSA construction
Date: Sun,  6 Aug 2017 22:26:51 +0200	[thread overview]
Message-ID: <20170806202651.8763-1-luc.vanoostenryck@gmail.com> (raw)

Since it seems to be some interest on the subject and
to avoid duplicated work, here is a rewrite of sparse's
construction of the SSA form.

It's not using one of the classical algorithm but is
using something newer, simpler and often faster.
It's main advantage beyond the simplicity is that you don't
need to first build the whole CFG & linearized code to
to directly throw it away (or heavily transform it) as
it builds the SSA form directly during the linearization.

It's not finished code but it's working well (and is
effectively a bit faster and use less memory).
What's interesting for sparse now is that:
- the phi-noes are correctly placed
- uninitialized variables can be handled much more easily.

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

             reply	other threads:[~2017-08-06 20:27 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-06 20:26 Luc Van Oostenryck [this message]
2017-08-06 23:01 ` [RFC] sparse SSA construction 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
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=20170806202651.8763-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).