[cfe-dev] Using clang as production compiler for chrome/mac

Nico Weber thakis at chromium.org
Sat Jul 9 17:34:48 PDT 2011


we're currently using clang for its diagnostics in chromium land, but
we'd like to use it to build our shipping binary in the future too.

One thing we're wondering about is which clang version to use for
this. Currently, we're pulling a fixed revision from the llvm svn
server and I update that revision about once a week.

One of the alternatives is to use trunk for our shipping binaries as
well. Chromium has three different channels – dev, beta, stable – and
we could use trunk for the dev channel and then branch clang with the
rest of our source for the beta and stable channels and only merge
"important" clang/llvm changes to there. Shipping a product that's
built with a potentially unstable compiler sounds a bit risky, so why
haven't I discarded this alternative already?

I imagine that it might be useful for the clang project, since we have
quite a bit of monitoring in chromium land (automated perf graphs,
compile time graphs, crash reporting that $many users have opted in
to), so that we could find and report regressions in clang reasonably
quickly. Do you think this is interesting at all?


More information about the cfe-dev mailing list