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: Adding an option to sparse to disable the IR simplifications
Date: Mon, 14 Aug 2017 13:09:46 -0400 [thread overview]
Message-ID: <CANeU7Qnxiz1x_VRRyYiN1PYXeB1zoH8-Qo3T8c0SWQ7HzhN88g@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxfND-vZ7zT9qN3q-ghckQByx_FFBOwykxL3Ff_skqSvEQ@mail.gmail.com>
On Mon, Aug 14, 2017 at 12:59 PM, Dibyendu Majumdar
<mobile@majumdar.org.uk> wrote:
>
> We can perhaps also move towards a granular level of control as in gcc
> or clang - i.e. enable or disable specific simplifications.
>
Yes, we can also do that. I I think the the back end should have some way
to control what kind of the optimization it want and what level it want etc.
I plan to release 0.5.1 finial on Wednesday. Then the merge windows is
open again. We can start to work on getting the IR right, getting SSA right etc.
I also have some patch want to merged as well like the ptrlist ref count.
It can even have a post release branch for experiment. After release
this branch will merge back to master.
Chris
prev parent reply other threads:[~2017-08-14 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 19:56 Adding an option to sparse to disable the IR simplifications Dibyendu Majumdar
2017-03-22 20:53 ` Dibyendu Majumdar
2017-08-14 16:38 ` Fwd: " Dibyendu Majumdar
2017-08-14 16:46 ` Luc Van Oostenryck
2017-08-14 16:59 ` Dibyendu Majumdar
2017-08-14 17:09 ` Christopher Li [this message]
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=CANeU7Qnxiz1x_VRRyYiN1PYXeB1zoH8-Qo3T8c0SWQ7HzhN88g@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).