<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Looks ok to me. <div><br></div><div>-Tanya</div><div><br><div><div>On Sep 9, 2011, at 11:42 AM, David Blaikie wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Just moving this over to the right commits list to hopefully get some visibility.<div><br><div class="gmail_quote">On Tue, Aug 30, 2011 at 10:08 PM, David Blaikie <span dir="ltr"><<a href="mailto:dblaikie@gmail.com">dblaikie@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div><div><blockquote type="cite"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Why not build a bunch of cross-compilers, and use the right one depending on the</div>
target? </blockquote><div><br></div><div>I honestly don't know what it takes to setup a cross compiler, and I wouldn't be the one doing it - I expect this would fall on Tanya's plate. <br></div></div></blockquote>
</div></div><br><div>Not worth the maintenance cost IMO.</div></div>
</blockquote></div><br></div>With that in mind, then, here's a modified version of Bjarke's patch that only provides 4 targets (x86, x86-64, llvm bitcode, llvm C++ api). I also stripped out Bjarke's work to support multiple front ends (llvm-gcc and clang) - I thought about preserving it or switching it to dragonegg, but I'm not sure that's worthwhile or in the domain of the llvm demo page. <br>
<br>& I stripped out some old file types/extensions that clang doesn't support (Java, Fortran) while I was here.<br><font color="#888888"><br>- David<br>
</font></blockquote></div><br></div>
<span><demo.diff></span></blockquote></div><br></div>
</body></html>