On Thursday, 3 May 2018 18:00:45 BST Corbin Bird wrote: > . > Chromium switched to 'clang++ v5.x' as its primary compiler. > Why? > The Chromium devs are using 'c++' features supported in gcc v8+. > . > So ... first compile run is with 'gcc' ... then Chromium is re-compiled > with 'clang++'. > That is what I am seeing ( console && log wise ). > 2 Compile runs ... twice the time. > . > No gold linker setup on my system. > Just how is 'clang++' supposed to work with 'ld.bfd'? > . > As far as I can tell, all optimization depending on '-march= / -mtune= ' > is still discarded, as well. > ( clang / clang ++, does not seem to accept the '-march= / -mtune= / -O2 > / -pipe' switches either. ) > . > Corbin
Thanks Corbin, it makes sense. Back in November build time jumped from 8 to 20 hours on my system. It's only gone further downhill since. :-( I will give USE="jumbo-build" a spin later to see what improvement I may get. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
