From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: Linux-Sparse <linux-sparse@vger.kernel.org>,
Christopher Li <sparse@chrisli.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: Fwd: Adding an option to sparse to disable the IR simplifications
Date: Mon, 14 Aug 2017 17:38:31 +0100 [thread overview]
Message-ID: <CACXZuxeyNL_OE0geog_TJPGtWj5TCP2CyX5UHeKxERvzsthbBw@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxdoLAW4rtk=zgwor9hVj8cxZ5GwSKGMSQUis_eWRiQ4GA@mail.gmail.com>
Hi,
I suggested a while back that it might be useful to add an option to
control the simplifications.
In dmrC the simplification phase is turned off by default. But if you
supply -O1 option then it is turned on. This ensures that I can test
both the unsimplified and simplified versions.
Regards
Dibyendu
---------- Forwarded message ----------
From: Dibyendu Majumdar <mobile@majumdar.org.uk>
Date: 22 March 2017 at 20:53
Subject: Re: Adding an option to sparse to disable the IR simplifications
To: Linux-Sparse <linux-sparse@vger.kernel.org>
On 22 March 2017 at 19:56, Dibyendu Majumdar <mobile@majumdar.org.uk> wrote:
> With the progress made with spars-llvm in recent weeks we are now
> beginning to hit bugs in the simplifications carried out by the
> linearizer. So it is useful I think to have an ability to turn off
> these modifications - perhaps by a command line argument. This will
> enable testing of sparse-llvm with and without the simplifications,
> and help identify issues caused by the latter phase.
>
It appears that there is already an optimize flag that is set by -O
option. Perhaps this flag can be utilized to control the level of
simplifications attempted.
Thanks and Regards
Dibyendu
next prev parent reply other threads:[~2017-08-14 16:38 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 ` Dibyendu Majumdar [this message]
2017-08-14 16:46 ` Luc Van Oostenryck
2017-08-14 16:59 ` Dibyendu Majumdar
2017-08-14 17:09 ` Christopher Li
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=CACXZuxeyNL_OE0geog_TJPGtWj5TCP2CyX5UHeKxERvzsthbBw@mail.gmail.com \
--to=mobile@majumdar.org.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--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).