From: Christopher Li <sparse@chrisli.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] avoid infinite loop during simplification
Date: Sat, 12 Aug 2017 10:34:26 -0400 [thread overview]
Message-ID: <CANeU7QnNeum7M0YrNP_amH82JED0c5GOGyVXQnj010e6mMhjdA@mail.gmail.com> (raw)
In-Reply-To: <CAExDi1SsOsdADxpMMBd+gc-HMkuZ0P0ozZT0A=JANPBz8O_k_A@mail.gmail.com>
On Sat, Aug 12, 2017 at 10:22 AM, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
> uh no.
> It's exactly how it's already working now.
> But it's exactly what is the problem when something
> silly, caused by an internal bug, change at *each*
> cycle and this it's what this patch avoid.
If there is change at each cycle then the change
flag will not help. I haven't seen those dead loop
so I did not know what is the nature of those.
I assume there is also other kind of deadloop
if we think there is some thing can CSE but no
actual change to the CFG.
>
> Of course, there is plenty of ways to do the same
> or something similar or something which will have
> the same result. This patch is just a very simple,
> no non-sense way to do it.
>
Sure. It is simple enough.
Chris
next prev parent reply other threads:[~2017-08-12 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-12 12:55 [PATCH] avoid infinite loop during simplification Luc Van Oostenryck
2017-08-12 13:55 ` Christopher Li
2017-08-12 14:04 ` Christopher Li
2017-08-12 14:22 ` Luc Van Oostenryck
2017-08-12 14:34 ` Christopher Li [this message]
2017-08-12 14:17 ` Luc Van Oostenryck
2017-08-12 14:31 ` Christopher Li
2017-08-12 14:50 ` Luc Van Oostenryck
2017-08-12 15:26 ` Christopher Li
2017-08-12 15:29 ` 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=CANeU7QnNeum7M0YrNP_amH82JED0c5GOGyVXQnj010e6mMhjdA@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
/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).