From: Christopher Li <sparse@chrisli.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
Dibyendu Majumdar <mobile@majumdar.org.uk>
Subject: Re: ptrlist-iterator performance on one wine source file
Date: Sat, 29 Jul 2017 12:30:16 -0400 [thread overview]
Message-ID: <CANeU7Q=gAZ9hQ8AGNkhZ8d_=kL5i9QdPsS_980dq+WHsOVW-oQ@mail.gmail.com> (raw)
In-Reply-To: <CANeU7QnHbCmpTmD7ckokE7XezHB6-ZAFzX-h+J8cPe=wWxx3VA@mail.gmail.com>
On Sat, Jul 29, 2017 at 12:25 PM, Christopher Li <sparse@chrisli.org> wrote:
> No I don't think so. The find dominator already taking the cycles into
> account. By definition if X dominate Y, means every execution flow
> from entry point to Y will need to go through X. If X was not reachable,
> nor does Y. It does not change where the block get deleted. It just don't
> not need to do the marking algorithm. That is the point of dominator tree.
Hold on I think I make a mistake there. You are right. It only work if
we already know
that block is dead. If there is cycles that block has incoming edges. Let's
me think about it. There should be better way to detect that is back edge.
Thinking.
Chris
next prev parent reply other threads:[~2017-07-29 16:30 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 15:05 ptrlist-iterator performance on one wine source file Christopher Li
2017-07-29 13:01 ` Luc Van Oostenryck
2017-07-29 15:53 ` Christopher Li
2017-07-29 16:04 ` Luc Van Oostenryck
2017-07-29 16:25 ` Christopher Li
2017-07-29 16:30 ` Christopher Li [this message]
2017-07-29 16:35 ` Luc Van Oostenryck
2017-07-29 19:33 ` Christopher Li
2017-07-29 21:47 ` Luc Van Oostenryck
2017-07-30 4:15 ` Christopher Li
2017-07-30 15:12 ` Luc Van Oostenryck
2017-07-30 15:49 ` Christopher Li
2017-07-30 16:16 ` Luc Van Oostenryck
2017-08-01 20:33 ` Luc Van Oostenryck
2017-08-01 21:09 ` Christopher Li
2017-08-01 21:46 ` Luc Van Oostenryck
2017-08-01 23:37 ` Christopher Li
2017-08-02 0:42 ` Christopher Li
[not found] ` <CANeU7QmzundH7qpdYhQqDJgBv+5pPemwft+1uH5oVQ1POnoQDw@mail.gmail.com>
2017-08-02 22:50 ` Luc Van Oostenryck
2017-08-03 21:49 ` Luc Van Oostenryck
2017-08-03 22:29 ` Luc Van Oostenryck
2017-08-03 22:35 ` Linus Torvalds
2017-08-04 0:04 ` Christopher Li
2017-08-04 0:11 ` Luc Van Oostenryck
2017-08-04 0:16 ` [PATCH] fix: give a type to bad conditionnal expressions Luc Van Oostenryck
2017-08-04 12:31 ` Luc Van Oostenryck
2017-08-04 14:52 ` Christopher Li
2017-08-04 14:53 ` Christopher Li
2017-08-04 11:33 ` ptrlist-iterator performance on one wine source file Luc Van Oostenryck
2017-08-04 14:51 ` Christopher Li
2017-08-04 22:26 ` Luc Van Oostenryck
2017-08-05 0:23 ` Christopher Li
2017-08-05 10:05 ` 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='CANeU7Q=gAZ9hQ8AGNkhZ8d_=kL5i9QdPsS_980dq+WHsOVW-oQ@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 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.