[cfe-dev] clang multi-threaded compiling

MLJ1991 via cfe-dev cfe-dev at lists.llvm.org
Fri Apr 2 03:58:51 PDT 2021


What build system are ou using? Ninja is built for parallel builds, and even with makefiles you can use -j X where X is the number of cores to parallize it.

in my expierence, the most expensive parts of compiling Clang is linking and running dysmutil for the debug symbols.

> On Apr 2, 2021, at 3:48 AM, James Courtier-Dutton via cfe-dev <cfe-dev at lists.llvm.org> wrote:
> 
> Hi,
> 
> I am working on a C++ project using Eclipse IDE.
> When I edit some code, and then go to debug it, it takes time to compile the one .cpp file I was editing, and then link it, and then the debugger starts.
> I have a 16 CPU Cores PC, but I have noticed for the use case:
> "one compile then one link"
> It is only using 1 CPU Core.
> It is therefore slow to cycle between edit code, and debug it.
> How do I get clang to use more than one core when compiling a single .cpp file?
> How do I get clang to use more than one core when linking?
> 
> Essentially, any way to speed up the "one compile then one link" use case would help me.
> 
> The build tool is "ninja", so a way for ninja to use clang in this way would help.
> 
> Kind Regards
> 
> James
> 
> 
> 
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev



More information about the cfe-dev mailing list