On 15/11/18 10:29, Richard Biener wrote: > In my view (I proposed the thing) the most interesting parts are > getting GCCs global state documented and reduced. The parallelization > itself is an interesting experiment but whether there will be any > substantial improvement for builds that can already benefit from make > parallelism remains a question.
in the common case (project with many small files, much more than core count) i'd expect a regression: if gcc itself tries to parallelize that introduces inter thread synchronization and potential false sharing in gcc (e.g. malloc locks) that does not exist with make parallelism (glibc can avoid some atomic instructions when a process is single threaded).
