Disable asserts in the Clang package
This allows the compiler to run a little faster. Clang will still be running with assertions enabled on the Clang tip-of-tree waterfall to catch regressions in Clang, or to catch existing asserts getting triggered by code that's checked into Chromium. Below are build times (each build was run twice to warm up the cache, and the second build time was noted) of the 'chrome' target configured with 'is_debug=false is_component_build=true'. Linux ----- asserts enabled: real 43m51.506s user 2304m36.334s sys 93m34.650s asserts disabled: real 36m37.976s (-16%) user 1910m47.627s sys 87m37.474s Windows ------- asserts enabled: peak memory: 2341.99MB real: 64m3.234s qpc: 3843245179us asserts disabled: peak memory: 2343.40MB real: 50m59.093s (-20%) qpc: 3059111587us Mac --- asserts enabled: real 175m19.768s user 3960m35.641s sys 168m42.376s asserts disabled: real 148m50.279s (-17%) user 3336m16.310s sys 171m51.878s It also reduces the size of the Clang package: 59M clang-356356-1-linux.tgz 33M clang-356356-1-mac.tgz 57M clang-356356-1-win.tgz 50M (-15%) clang-356356-2-linux.tgz 28M (-15%) clang-356356-2-mac.tgz 45M (-21%) clang-356356-2-win.tgz Bug: 896306 Change-Id: I26068467119065a9d381f7f97f8dfac1defeb309 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1532107Reviewed-by:Nico Weber <thakis@chromium.org> Commit-Queue: Nico Weber <thakis@chromium.org> Cr-Commit-Position: refs/heads/master@{#645377}
Showing
Please register or sign in to comment