Optimize compilation of mojo .cc files that contain no code
When building the 'chrome' target Mojo generates about 680 .cc files that contain no actual code. Due to the includes that are stamped out these files collectively take a non-trivial amount of time to compile. Detecting these files and deleting the #includes saves about ~1,200 to ~2,100 CPU seconds. The no-code detection doesn't work generically, but it handles the code which mojo generates. Bug: 1054626 Change-Id: Icb2feaa0021332e0a6d4c9e5cac314824578cd87 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2093881Reviewed-by:Ken Rockot <rockot@google.com> Commit-Queue: Bruce Dawson <brucedawson@chromium.org> Cr-Commit-Position: refs/heads/master@{#748711}
Showing
Please register or sign in to comment