Linked by Thom Holwerda on Tue 6th Mar 2018 20:08 UTC

As of Chrome 64, Chrome for Windows is compiled with Clang. We now use Clang to build Chrome for all platforms it runs on: macOS, iOS, Linux, Chrome OS, Android, and Windows. Windows is the platform with the second most Chrome users after Android according to statcounter, which made this switch particularly exciting.

Thread beginning with comment 654361
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: slow decline of GCC ?
by dylansmrjones on Thu 8th Mar 2018 01:31 UTC in reply to "RE: slow decline of GCC ?"
Member since:

Reverse is true for me. I get shorter compilation times with gcc for chromium than with clang (still takes some hours). Otoh, anything obj-c is done with clang. There's no compelling technical reasons to choose one over the other in general. As is evident from assorted tests and comparisons. I rely on both.

Reply Parent Score: 3

ahferroin7 Member since:

Interesting. I've never built Chromium with Clang, but I have done webkit-gtk and Firefox with it before, and both of those built faster. I've not tried recently though, and performance of GCC may have significantly improved since I last tried.

Reply Parent Score: 2