From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Christopher Li <sparse@chrisli.org>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [RFC] sparse SSA construction
Date: Wed, 16 Aug 2017 14:28:50 +0200 [thread overview]
Message-ID: <CAMHZB6Es+y+xCGMOrd=gvsqiTVWgz3niOXOQrv3fTFzr=6akVA@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxfd074S1jJMotGzn=MK-RORU7DEe7uj_yQ7oZPeyxVF9g@mail.gmail.com>
On Wed, Aug 16, 2017 at 2:16 PM, Dibyendu Majumdar
<mobile@majumdar.org.uk> wrote:
>
> Is it the problem that you are constructing SSA while linearizing - so
> that you do not have the gotos resolved? Would it be a better design
> to finish linear stream, and then run SSA conversion?
The *big* advantage of this method is that you *do not* have to first
generate the whole thing *and then* transform it into SSA form.
The price is a slight complication in the handling of gotos.
The more classic approach need special handling for gotos too.
-- Luc
next prev parent reply other threads:[~2017-08-16 12:28 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 [this message]
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='CAMHZB6Es+y+xCGMOrd=gvsqiTVWgz3niOXOQrv3fTFzr=6akVA@mail.gmail.com' \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=mobile@majumdar.org.uk \
--cc=sparse@chrisli.org \
--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.