Issue metadata
Sign in to add a comment
|
Make chrome/android built with clang by default, mips32 and mips64 |
||||||||||||||||||||||||
Issue descriptionWe want to switch chrome/android to build with clang by default. We want to use the autoupdating compiler stuff we use everywhere. To make sure that upstream clang compiler changes don't break chrome, we have bots building and testing chrome with clang trunk (https://build.chromium.org/p/chromium.fyi/console?category=clang%20tot). We don't have any mips devices that we run tests on (either on that waterfall or anywhere else). I suppose we can add a bot that at least compiles, which gives some coverage. I don't know how binary size or perf compares to gcc on mips. I don't know if any mips folks want to do any evaluation before we switch. See other blockers of linked bug for other platforms.
,
Oct 17 2016
There are some ongoing build issues for MSA built-ins with clang 4.0.0 (Available at chromium/src/third_party/llvm-build/Release+Asserts/bin/clang) And i believe upstream of LLVM fixes is also in progress. There seems no issues in adding mips32/mips64 bots (disabling msa) as of now as those builds fine. We can start with mips32/64 builds and enable msa once clang build issues gets fixed. For running tests, is it possible to setup QEMU for linux from ? http://codescape-mips-sdk.imgtec.com/components/qemu/2.5.0.2.0/ Thanks,
,
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