<div dir="ltr">On Fri, Aug 16, 2013 at 2:01 PM, reed kotler <span dir="ltr"><<a href="mailto:rkotler@mips.com" target="_blank">rkotler@mips.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">the good news is that (thanks to Simon) the clang driver is working so well for Mips now that we are more or less switching away from using llc during development for all our various host/target configurations.<br>
<br>
the bad news is that we have make clang all the time and it is really slow to do that.<br>
<br>
we used to be able to just make in the lib/target/Mips and then in llc and it was really fast.<br>
<br>
part of it is probably that we have all this debug information that we don't need because none of use are working on clang itself (well, almost never).<br>
<br>
ideas?<br>
<br>
for 99% of our changes we are just editting files in libc/target/Mips<br>
<br>
what is the fastest way to get a new clang complete compiler after that?<br><br></blockquote><div><br></div><div>What exactly is slow? I mean, if you're worried about build system overhead, if you haven't made any changes to clang, you can run "make" in clang/tools/driver/ . If the issue is really the debug info, I'm not sure what I can suggest...</div>
<div><br></div><div>-Eli</div></div></div></div>