<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
That's rather disappointing to read that you don't intende to change
the Linux build to Clang.<br>
<br>
One would assume when Concurrency work is done in Clang that you'd
make the switch. The more projects move to LLVM/Clang the less the
number of dependencies arise, unlike the behemoth that has become
the GCC Collection. The number of packages alone in Debian, Ubuntu,
Redhat and others is just absurd.<br>
<br>
If you offer clang built Linux versions for Debian with their
FreeBSD project I'm sure the appreciation would be well received.<br>
<br>
I'll be pushing for GNOME to move more of it's infrastructure to
LLVM/Clang as well.<br>
<br>
If Qt makes LLVM/Clang a first class citizen to build it's
frameworks it would go a long way for the KDE Project to make their
infrastructure LLVM/Clang friendly.<br>
<br>
Yet, differentiating Chrome from being built with clang formally on
Linux and even Windows seems a more political solution than a
technical one.<br>
<br>
- Marc<br>
<br>
On 10/28/2011 02:01 PM, Nico Weber wrote:
<blockquote
cite="mid:CAMGbLiG+gj-46hP_zHoH2_ANcp8ngsrM7F7zRK8E3m9Hc-cGDw@mail.gmail.com"
type="cite">
<pre wrap="">Hi,
I think I never sent an official announcement to this list, so here
goes: Starting with chrome 15, which was released this week, the
official chrome/mac binary is built with clang. We also use clang on
all our mac buildbots, and stopped supporting gcc 4.2. Chrome's
performance stayed the same after the switch (but many of the
performance numbers we measure are in v8-jitted code), and the
uncompressed binary size went down 10%.
The official chrome/linux is still built with gcc, and we don't intend
to change that, but we have a clang builder on linux as well, for
clang's diagnostics.
We do a build of trunk clang every friday, and use this to build the
development versions of chrome/mac. When we branch for a release, the
current plan is to create a branch in the clang repo as well and merge
critical clang fixes there if the need arises. For chrome 15, it looks
like we picked a revision that didn't need any fixes, so we didn't
create any branches so far.
Nico
ps: The binaries we use to build chrome are available at
<a class="moz-txt-link-freetext" href="http://commondatastorage.googleapis.com/chromium-browser-clang/index.html">http://commondatastorage.googleapis.com/chromium-browser-clang/index.html</a>
_______________________________________________
cfe-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cfe-dev@cs.uiuc.edu">cfe-dev@cs.uiuc.edu</a>
<a class="moz-txt-link-freetext" href="http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev">http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev</a>
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
Marc J. Driftmeyer<br>
Email :: <a href="mailto:mjd@reanimality.com">mjd@reanimality.com</a><br>
Web :: <a href="http://www.reanimality.com">http://www.reanimality.com</a><br>
Cell :: (509) 435-5212
</div>
</body>
</html>