Command to run:
tools/binary_size/diagnose_bloat.py --cloud c8a7216a351ff121d661f5fa87b1c0e79fbd3935
*However*, there's a bug in Supersize making the number not add up (found the cause and will fix tomorrow). Examining the binary shows that many symbols that were previously aliased (i.e., compiled into the same binary) now became independent functions. The many bytes then add up to 22 KiB bloat. Can this be fixed by tweaking templates somehow?
Thanks! We currently have two methods that describe the pointers of an object for Oilpan. This CL merges calls into a single one, so more size is expected.
Maybe we can tweak templates a bit but the real fix is removing the now obsolete method across the whole code base. I've drafted this in https://chromium-review.googlesource.com/c/chromium/src/+/1074987 but probably need to split it among a few CLs because it touches so many files that merge conflicts are unavoidable without closing the tree.
Will address this bug and run the diagnose bloat script for each of those CLs.
Comment 1 by 42576172...@developer.gserviceaccount.com
, May 28 2018