<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 22, 2013, at 11:29 AM, Eli Bendersky <<a href="mailto:eliben@google.com">eliben@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Mar 22, 2013 at 11:25 AM, Chandler Carruth <span dir="ltr"><<a href="mailto:chandlerc@google.com" target="_blank">chandlerc@google.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="im">On Fri, Mar 22, 2013 at 10:47 AM, Andrew Trick <span dir="ltr"><<a href="mailto:atrick@apple.com" target="_blank">atrick@apple.com</a>></span> wrote:<br>
</div><div class="gmail_extra"><div class="gmail_quote"><div class="im">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><div><div>On Mar 22, 2013, at 9:14 AM, Eli Bendersky <<a href="mailto:eliben@google.com" target="_blank">eliben@google.com</a>> wrote:</div>
<br><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Thu, Mar 21, 2013 at 7:24 PM, Chandler Carruth <span dir="ltr"><<a href="mailto:chandlerc@google.com" target="_blank">chandlerc@google.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">FYI, I reverted the patch in r177695 to fix our builds. We check that layering violations don't get any worse in our build system.</div>
</blockquote><div><br></div><div>Can you explain what kind of build this breaks?</div><div><br></div><div>I understand the layering problem, but how do we still get to measure the time IR parsing took? Do you have plans to fix the IR Reader violation any time soon?</div>
</div></div></div></blockquote><div><br></div></div>To answer your middle question. Just reuse -time-passes and expose the flag in LLVMContext.</div><div><br></div><div>On the last question, I would like to see an answer to Chandler's question about whether anyone cares if they now automatically link the IR parser. Maybe Chandler should re-ask on llvm-dev?</div>
</div></blockquote><div><br></div></div><div>Chatted with Chris on IRC and he seemed happier with a new library. I'm adding that now.</div><div><br></div><div>It's called "IRReader" so we have IRReader/IRReader.h... if anyone really wants a different name, shout...</div>
</div></div></div></blockquote><div><br></div><div style="">So should the flag go back to IRReader or to LLVMContext? I still think it makes sense to have it separate because we have a bunch of LLVM tools that read IR but don't run any "passes".</div></div></div></div></blockquote><div><br></div><div>Back now to Nadav's original question. Why do we need a new command line flag? I don't see a good reason. If someone want to -time-passes, I think they'll be happy to get IR parsing time too. If the tool doesn't run formal passes, then it just shows parsing time and any other times the tool chooses to add under the TimePassesIsEnabled flag.</div><div><br></div><div>-Andy</div><div><br></div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div style="">Chandler - are you going to add the timing back in when you create a new lib? If not let me know when it's good time to put it back in after you're done.</div><div style=""><br></div><div st!
yle="">
Eli</div><div><br></div><div> </div></div></div></div>
</blockquote></div><br></body></html>