| commit | 0944cd856079ec2f45cb5f1f1e085ff054e16f08 | [log] [tgz] |
|---|---|---|
| author | Josh Haberman <jhaberman@gmail.com> | Wed Aug 04 15:12:49 2021 -0700 |
| committer | Josh Haberman <jhaberman@gmail.com> | Wed Aug 04 15:18:03 2021 -0700 |
| tree | 628e02ff4601c36b6f159e2e1e532ae6c95525f4 | |
| parent | 61a56fae070ca1e0c23adc79497c7ad971e09b62 [diff] |
Split and updated the docs.
Ever wondered what‘s making your binary big? Bloaty will show you a size profile of the binary so you can understand what’s taking up space inside.
Bloaty performs a deep analysis of the binary. Using custom ELF, DWARF, and Mach-O parsers, Bloaty aims to accurately attribute every byte of the binary to the symbol or compileunit that produced it. It will even disassemble the binary looking for references to anonymous data. For more information about the analysis performed by Bloaty, please see doc/how-bloaty-works.md.
Bloaty works on binaries, shared objects, object files, and static libraries (.a files). The following file formats are supported:
This is not an official Google product.
To build, use cmake. For example:
$ cmake -G Ninja . $ ninja
Bloaty bundles libprotobuf, re2, capstone, and pkg-config as Git submodules, and uses protoc build from libprotobuf, but it will prefer the system's versions of those dependencies if available. All other dependencies are included as Git submodules.
If the Git repository hasn't been cloned with the --recursive, the submodules can be checked out with:
$ git submodule update --init --recursive
To run the tests, see the info in tests/README.md.
Here are some tentative plans for future features.
If we can analyze references between symbols, this would enable a lot of features:
-ffunction-sections -fdata-sections -Wl,-gc-sections).ld -why_live on OS X).