News for hackers. Stuff that matters.
Re:How to C in 2016 by tsavola on Friday January 08, 2016 @07:19AM (#10864337)
> LTO fixes the "source analysis and optimization across compilation units problem" by annotating object files with intermediate representation so source-aware optimizations can be carried out across compilation units at link time (this slows down the linking process noticeably, but make -j helps).

make -j doesn't help linking speed, unless multiple binaries are begin built.

Re:How to C in 2016 by lorenzhs on Friday January 08, 2016 @09:24AM (#10865006)
gcc has `-flto=n` to use n cores for the link-time optimization. clang doesn't like that syntax though, but I think it does parallel LTO automatically.
Re:How to C in 2016 by delinka on Friday January 08, 2016 @08:05AM (#10864543)
It's not the linking process that make -j speeds up, but the optimization part.
Re:How to C in 2016 by tsavola on Friday January 08, 2016 @08:45AM (#10864734)
AFAIK the bulk of link time optimization happens in the linker. The parallelizable compiler invocations just store extra information in the object files.

The linker invocation is a single make job, which is the unit of make -j parallelism.