<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="">Do you have any details on how it broke? If I can see the symptom, I might be able to guess at the cause.<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 18, 2014, at 3:10 PM, Reid Kleckner <<a href="mailto:rnk@google.com" class="">rnk@google.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I had to revert this patch in <span style="" class="">r224546, as it broke compilation of fortran files with gcc through the clang driver. It's easy to observe the change in behavior with -###, but I think you need to be on a system where clang thinks there is a valid gcc installation that can handle fortran. I was unable to observe the behavior change on Windows, for example, so I doubt it will be observable on Mac OS X without some fiddling. Let me know if you need help reproducing the situation.</span></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Mon, Dec 15, 2014 at 4:19 PM, Bob Wilson <span dir="ltr" class=""><<a href="mailto:bob.wilson@apple.com" target="_blank" class="">bob.wilson@apple.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" 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" target="_blank" class="">dblaikie@gmail.com</a>> wrote:</div><br class=""><div class=""><div dir="ltr" class=""><br class=""><div class="gmail_extra"><br class=""><div class="gmail_quote"><div class=""><div class="h5">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></div><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><span class=""><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></span><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><br class="">_______________________________________________<br class="">
cfe-dev mailing list<br class="">
<a href="mailto:cfe-dev@cs.uiuc.edu" class="">cfe-dev@cs.uiuc.edu</a><br class="">
<a href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev" target="_blank" class="">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a><br class="">
<br class=""></blockquote></div></div>
</div></blockquote></div><br class=""></div></body></html>