<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 15, 2014, at 4:19 PM, Bob Wilson <<a href="mailto:bob.wilson@apple.com" class="">bob.wilson@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 15, 2014, at 3:06 PM, David Blaikie <<a href="mailto:dblaikie@gmail.com" class="">dblaikie@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, Dec 15, 2014 at 3:00 PM, Diego Novillo <span dir="ltr" class=""><<a href="mailto:dnovillo@google.com" target="_blank" class="">dnovillo@google.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><p dir="ltr" class=""><br class="">
On Dec 15, 2014 5:23 PM, "David Blaikie" <<a href="mailto:dblaikie@gmail.com" target="_blank" class="">dblaikie@gmail.com</a>> wrote:<br class="">
><br class="">
><br class="">
><br class="">
> On Mon, Dec 15, 2014 at 1:09 PM, Diego Novillo <<a href="mailto:dnovillo@google.com" target="_blank" class="">dnovillo@google.com</a>> wrote:<br class="">
>><br class="">
>> On 12/15/14 15:10, Joerg Sonnenberger wrote:<br class="">
>>><br class="">
>>> On Mon, Dec 15, 2014 at 11:26:43AM -0800, Bob Wilson wrote:<br class="">
>>>><br class="">
>>>> Does anyone have interest in this or objections to it?<br class="">
>>><br class="">
>>><br class="">
>>> Yes, please. Especially if it captures the bitcode *before* any of the<br class="">
>>> optimisations hit.<br class="">
>><br class="">
>><br class="">
>> Agreed. On several occasions, I've found myself wondering how I can generate bitcode exactly as it leaves the parser, before any early cleanups and such.<br class="">
><br class="">
><br class="">
> -mllvm -disable-llvm-optzns<br class="">
><br class="">
> will produce the IR straight out of Clang's CodeGen. Skipping things like the AlwaysInliner and AddDiscriminator pass, etc.<br class="">
> </p>
</span><p dir="ltr" class="">Yes. Of course, i know that. </p></blockquote><div class="">Ah, sorry - wasn't sure if you knew that particular one. I always forget it/have to look it up whenever I want to do that. </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr" class="">The point is that easier is better.<br class=""></p></blockquote><div class="">Sure enough - well, point to Bob, then: consider doing this kind of IR, rather than the usual -emit-llvm IR, to get something closer to the original/pure generated IR.<br class=""></div></div></div></div></div></blockquote></div><br class=""><div class="">Sounds good. I agree that will be even more useful. Steven Wu has already written a patch to do something similar, so I’ll see if I get that done soon.</div></div></div></blockquote><br class=""></div><div>I’ve committed a change to implement this in r224503. Please try it out and let me know if it is not doing what you expect.</div><br class=""></body></html>