| 1 |
On Thursday, 3 May 2018 18:00:45 BST Corbin Bird wrote: |
| 2 |
> . |
| 3 |
> Chromium switched to 'clang++ v5.x' as its primary compiler. |
| 4 |
> Why? |
| 5 |
> The Chromium devs are using 'c++' features supported in gcc v8+. |
| 6 |
> . |
| 7 |
> So ... first compile run is with 'gcc' ... then Chromium is re-compiled |
| 8 |
> with 'clang++'. |
| 9 |
> That is what I am seeing ( console && log wise ). |
| 10 |
> 2 Compile runs ... twice the time. |
| 11 |
> . |
| 12 |
> No gold linker setup on my system. |
| 13 |
> Just how is 'clang++' supposed to work with 'ld.bfd'? |
| 14 |
> . |
| 15 |
> As far as I can tell, all optimization depending on '-march= / -mtune= ' |
| 16 |
> is still discarded, as well. |
| 17 |
> ( clang / clang ++, does not seem to accept the '-march= / -mtune= / -O2 |
| 18 |
> / -pipe' switches either. ) |
| 19 |
> . |
| 20 |
> Corbin |
| 21 |
|
| 22 |
Thanks Corbin, it makes sense. Back in November build time jumped from 8 to |
| 23 |
20 hours on my system. It's only gone further downhill since. :-( |
| 24 |
|
| 25 |
I will give USE="jumbo-build" a spin later to see what improvement I may get. |
| 26 |
|
| 27 |
-- |
| 28 |
Regards, |
| 29 |
Mick |
Archives