On Wed, Jul 11, 2012 at 10:10 AM, Peter Cooper <span dir="ltr"><<a href="mailto:peter_cooper@apple.com" target="_blank" class="cremed">peter_cooper@apple.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This is excellent Chandler.<br>
<br>
We spoke before about wanting to keep running things like InstCombine and SimplifyCFG in a loop until stabilization. This will make doing that much easier.<br>
<br>
I think some of the idea for this work might have come from a patch i tried to submit a few weeks ago on reducing recomputing the dom tree, in which you commented that we need to fix the pass manager.</blockquote><div><br>
</div><div>Well, my interest was renewed sharply when I wrote a significant optimization pass that simply cannot run in the existing framework. =/</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
In that email i mentioned that not all passes respect the return value from runOnFunction. Is your pass framework going to explicitly use this return value? If so we'll need everyone to help make sure passes correctly return when they change anything.<br>
</blockquote><div><br></div><div>I *really* want to make this happen, but I think it needs to happen as a phase-2. For now, I think we have to replicate the annoying current behavior.</div></div></div>