[LLVMdev] workflow for linking clang

[reed kotler]

On 08/16/2013 02:13 PM, Eli Friedman wrote:
> On Fri, Aug 16, 2013 at 2:01 PM, reed kotler <rkotler at mips.com 
> <mailto:rkotler at mips.com>> wrote:
>
>     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.
>
>     the bad news is that we have make clang all the time and it is
>     really slow to do that.
>
>     we used to be able to just make in the lib/target/Mips and then in
>     llc and it was really fast.
>
>     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).
>
>     ideas?
>
>     for 99% of our changes we are just editting files in libc/target/Mips
>
>     what is the fastest way to get a new clang complete compiler after
>     that?
>
>
> 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...
>
> -Eli
the initial build is not an issue. it's the rebuilding

so if i do a make in lib/Target/Mips then I should just be able to do a 
make in the clang/tools/driver directory?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130816/f0ff4e7b/attachment.html>