Bloaty is a binary size profiler and executable format analyzer that attributes every byte of a binary to specific symbols or compile units. It functions as a compilation unit profiler and C++ symbol demangler, mapping binary size back to source files and translating mangled names into human-readable formats.
The main features of google/bloaty are: Binary Size Regression Tracking, Debug Symbol Resolvers, Compilation Unit Profilers, Stripped Binary Debugging Tools, Executable Format Support, Byte-Level Symbol Attribution, Binary Diffing, Executable Format Analyzers.
Open-source alternatives to google/bloaty include: kdab/hotspot — Hotspot is a graphical user interface for analyzing and visualizing performance data captured by the Linux perf tool.… razrfalcon/cargo-bloat — cargo-bloat is a binary size analyzer and compilation analysis tool for Rust. It identifies the largest functions and… microsoft/binskim — A binary static analysis tool that provides security and correctness results for Windows Portable Executable and *nix… jkinder/jakstab — The Jakstab static analysis platform for binaries. horsicq/nauz-file-detector — Linker/Compiler/Tool detector for Windows, Linux and MacOS. rustwasm/twiggy — Twiggy🌱 is a code size profiler.
Hotspot is a graphical user interface for analyzing and visualizing performance data captured by the Linux perf tool. It functions as a performance profiling visualizer and assembly-level profiler that maps performance costs to specific instructions synchronized with original source code. The project distinguishes itself through a remote symbol resolver that maps performance data from embedded targets to local host debug symbols and sysroots. It also includes a specialized off-CPU analysis tool designed to identify thread wait times and I/O blocks using kernel scheduler tracepoints. The tool
cargo-bloat is a binary size analyzer and compilation analysis tool for Rust. It identifies the largest functions and dependencies within compiled executables to locate space-consuming code and reduce the overall binary footprint. The tool functions as a build profile inspector and symbol size profiler, allowing users to analyze how different compiler options and build profiles affect the final binary size. It can export symbol data into human-readable tables or JSON format to monitor the footprint of specific crates. Capabilities include multi-target analysis across different platforms and
Linker/Compiler/Tool detector for Windows, Linux and MacOS.