<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 26, 2011, at 5:26 PM, David Blaikie wrote:</div><br class="Apple-interchange-newline"><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><div class="h5">> Seems someone else got to this a while ago, but perhaps didn't quite<br>
> get enough feedback or have enough time to see it through:<br>
><br>
> <a href="http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-March/038828.html" target="_blank">http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-March/038828.html</a><br>
> <a href="http://llvm.org/bugs/show_bug.cgi?id=1440" target="_blank">http://llvm.org/bugs/show_bug.cgi?id=1440</a><br>
><br>
> If someone wants to give feedback on the changes posted in the bug I<br>
> can try to update it, or we can start again from scratch.<br>
><br>
> I'm just working on getting this setup myself so I can see how it<br>
> looks/works locally.<br>
<br>
</div></div>Aha, this is the problem with attaching patches to bugs: noone sees them. It is *much much* better to send patches to a -commits list.<br>
<br>
The patch looks like reasonable progress to me!</blockquote><div><br></div></div><div>So, colored clang diagnostics finally work :) & as a side-benefit, I got around to setting up my own demo test area (it actually wasn't too painful at all - the cgi script's fairly standalone, just had to point it to my llvm install & away it went - great) so I should be able to prototype stuff there & submit fairly sane patches directly against www/demo/index.cgi without too much churn.<br>
</div><div><br></div><div>So, now to figure out what to do with the page. The bug/patch I mentioned above seems to still have some outstanding issues (given the discussion in the bug itself) - cross compiling on the demo machine/website won't come for free. Any ideas on what we should do there? Should we actually get the demo machine setup with all the necessary libs/things to do real cross compilation?</div>
<div><br></div></blockquote><div><br></div><div>I wonder what the real benefit is here though versus the cost? If we are just trying to give a quick demo of LLVM/Clang, then how much value is in supporting multiple targets?</div><div><br></div><div>Also, whats the benefit in demoing targets that are not officially supported by releases?</div><div><br></div><blockquote type="cite"><div>I'd like to roll in whatever work was already done for that patch that's actually applicable before I go forward with my own ideas. But for myself, the first thing I'd work on (& have worked up partially on my prototype site) is C++ version selection (could be generalized to all language versions supported by clang) and library selection (would require libc++ to be installed on the demo server, if it's not already there). <br></div></blockquote><div><br></div><div>I do think there are many things we could be displaying that Clang supports that we are not. </div><br><blockquote type="cite"><div>
Any particular end goal you have in mind that would be worth doing some up-front design for, or is it good to just go adding these little bits on here & there & then try to redesign if we see a way to make it all fit together better?</div></blockquote><div><br></div><div>I personally don't have any ideas for the demo page, but anything you come up with I say go ahead and prototype if its small and anything large, I'd send to the list for discussion before spending a lot of time on it. I'm sure some of the active Clang developers may have opinions.</div><div><br></div><div>Thanks,</div><div>Tanya</div><br><blockquote type="cite">
<div><br></div><div>- David</div>
</blockquote></div><br></body></html>