On Wed, Mar 2, 2016 at 3:15 PM, Jeff Gilbert <jgilb...@mozilla.com> wrote:
> For standard development builds, --enable-debug build speed is (to me) > the primary motivator since we've guaranteed that they're equally > correct. (within reason) I'll gladly run some extra tests to gather > data about this. > > FWIW, with a 26% speedup, it would definitely seems like it'd be worth > investigating also for automation. Is anyone/anybug driving that? > Automation is a trickier subject because if we change the "official" toolchain that has implications for down-stream packagers, who will likely want to follow suit. I'd rather keep our scope limited to developer builds for now so we postpone opening the can of worms. Also, glandium claims GCC is a bit better with ccache. And given our higher cache hit rate in automation due to using S3 as a global cache, that may make GCC faster than Clang in automation. Need moar data. > > On Wed, Mar 2, 2016 at 2:50 PM, Gregory Szorc <g...@mozilla.com> wrote: > > Over in bug 1253064 I'm proposing switching developer builds to prefer > > Clang over GCC because the limited numbers we have say that Clang can > build > > mozilla-central several minutes faster than GCC (13 minutes vs 17.5 on my > > I7-6700K). I'm not proposing switching what we use to produce builds in > > automation. I'm not proposing dropping GCC support. This is all about > > choosing faster defaults so people don't spend as much time waiting for > > builds to complete and become more productive as a result. > > > > Please comment on the bug if you have something to add. > > _______________________________________________ > > dev-platform mailing list > > dev-platform@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
