tools/binary_size/README.md - Issue 2880003002: supersize: A few fixes for Android+clang builds

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: tools/binary_size/README.md

Issue 2880003002: supersize: A few fixes for Android+clang builds (Closed)

Patch Set: rebase Created 3 years, 7 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch

« no previous file with comments | « no previous file | tools/binary_size/libsupersize/archive.py » ('j') | no next file with comments »

OLD	NEW
1 # Tools for Analyzing Chrome's Binary Size	1 # Tools for Analyzing Chrome's Binary Size

2	2

3 These currently focus on Android and Linux platforms. However, some great tools	3 These tools currently focus on Android compiled with GCC. They somewhat work

4 for Windows exist and are documented here:	4 for Android + Clang, and Linux builds, but not as well. As for Windows, some

	5 great tools already exist and are documented here:

5	6

6 * https://www.chromium.org/developers/windows-binary-sizes	7 * https://www.chromium.org/developers/windows-binary-sizes

7	8

8 There is also a dedicated mailing-list for binary size discussions:	9 There is also a dedicated mailing-list for binary size discussions:

9	10

10 * https://groups.google.com/a/chromium.org/forum/#!forum/binary-size	11 * https://groups.google.com/a/chromium.org/forum/#!forum/binary-size

11	12

12 [TOC]	13 [TOC]

13	14

14 ## diagnose_bloat.py	15 ## diagnose_bloat.py

(...skipping 160 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
175 * Show symbol counts by bucket size.	176 * Show symbol counts by bucket size.

176 * 3 symbols < 64 bytes. 10 symbols < 128, 3 < 256, 5 < 512, 0 < 1024, 3 < 2 048	177 * 3 symbols < 64 bytes. 10 symbols < 128, 3 < 256, 5 < 512, 0 < 1024, 3 < 2 048

177 1. More `html_report` features:	178 1. More `html_report` features:

178 * Able to render size diffs (tint negative size red).	179 * Able to render size diffs (tint negative size red).

179 * Break down by other groupings (Create from result of `SplitByName()`)	180 * Break down by other groupings (Create from result of `SplitByName()`)

180 * Render as simple tree view rather than 2d boxes	181 * Render as simple tree view rather than 2d boxes

181 1. Integrate with `resource_sizes.py` so that it tracks size of major	182 1. Integrate with `resource_sizes.py` so that it tracks size of major

182 components separately: chrome vs blink vs skia vs v8.	183 components separately: chrome vs blink vs skia vs v8.

183 1. Add dependency graph info, perhaps just on a per-file basis.	184 1. Add dependency graph info, perhaps just on a per-file basis.

184 * No idea how to do this, but Windows can do it via `tools\win\linker_verbose _tracking.py`	185 * No idea how to do this, but Windows can do it via `tools\win\linker_verbose _tracking.py`

OLD	NEW