<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 22, 2016 at 5:50 PM, Friedman, Eli <span dir="ltr"><<a href="mailto:efriedma@codeaurora.org" target="_blank">efriedma@codeaurora.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">
<div>On 8/22/2016 11:28 AM, Daniel Berlin
via llvm-commits wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">+philip because he expressed concerns around
limiting
<div><br>
</div>
<div>+eli
<div><br>
</div>
<div>Eli, i think your patch to DSE to do exact may-throw
tracking is what made this worse.</div>
<div><br>
</div>
</div>
<div><a href="https://llvm.org/bugs/show_bug.cgi?id=29064" target="_blank">https://llvm.org/bugs/show_<wbr>bug.cgi?id=29064</a><br>
</div>
</div>
</blockquote>
<br></span>
I don't think it's the fault of my recent patch.</div></blockquote><div> </div><div>Okay.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"> The stack trace
from that bug points into MemDep, not my new code, </div></blockquote><div><br></div><div>Well, to be fair, both are calling PointerMayBeCaptured, which is the expensive part of this.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000">and the patch
which fixes it doesn't touch my new code.<span class=""><br>
<br></span></div></blockquote><div>Fair enough.</div><div><br></div><div><br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><span class="">
<blockquote type="cite">
<div dir="ltr">
<div>I'm not sure we should limit DSE.</div>
</div>
</blockquote>
<br></span>
An arbitrary limit isn't exactly ideal, but there probably isn't any
better way to fix the issue given the current algorithm used by DSE
and MemDep.<br></div></blockquote></div></div></div>