Issue metadata
Sign in to add a comment
|
Make chrome/android built with clang by default, x64 |
||||||||||||||||||||
Issue descriptionthakis@thakis:~/src/chrome/src$ ls -hl out/gnand3/libchrome.so -rwxr-x--- 1 thakis eng 70M Oct 11 11:38 out/gnand3/libchrome.so is_clang = true thakis@thakis:~/src/chrome/src$ ls -hl out/gnand4/libchrome.so -rwxr-x--- 1 thakis eng 69M Oct 10 16:49 out/gnand4/libchrome.so (first is gcc, second is clang) This looks like it's ready to go (and it's the config we already ship clang-built binaries in on mac and linux), only blocked on getting clang tot coverage for this. ⛆ |
|
|
,
Oct 17 2016
(blocker is being worked on)
,
Oct 31 2016
,
Oct 31 2016
I just learned that we also build a x86 binary as part of the x64 build. While x86 is still being built by gcc, we probably want to also build the x86 binary built as part of the x64 build with gcc even when switching the x64 binary to clang (see bug 605315 )
,
Nov 1 2016
,
Nov 2 2016
,
Nov 2 2016
,
Nov 2 2016
,
Nov 2 2016
,
Nov 21 2016
With -Wl,--icf=safe with clang due to bug 663886 : thakis@thakis:~/src/chrome/src$ ls -hl out/gnand4/libchrome.so -rwxr-x--- 1 thakis eng 75M Nov 21 16:35 out/gnand4/libchrome.so thakis@thakis:~/src/chrome/src$ ls -hl out/gnand3/libchrome.so -rwxr-x--- 1 thakis eng 72M Nov 21 16:21 out/gnan :-/
,
Jun 14 2017
We ended up switching all archs at once after all. |
||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by thakis@chromium.org
, Oct 14 2016