We’re launching Lyria 3.5 in Google Flow Music, with advances across musicality, lyrics, vocals, and creative control
deepmind.google·6d ago
AI Engineering
Lobsters·16d ago·5 min read
CodeSizer: Why is that binary so big?
TL;DR
CodeSizer addresses the challenge of large binary sizes in embedded firmware by analyzing inline functions. It utilizes objdump and addr2line to trace the inline call stack, attributing code size accurately.
✦ Why It Matters
Engineers can implement CodeSizer today to analyze and optimize their firmware binaries for size reduction.
Key Takeaways
- Utilize CodeSizer to analyze binary sizes in embedded firmware.
- Specify ELF sections to focus on relevant code areas.
- Ensure the correct toolchain is in your system's PATH.
- Generate interactive HTML reports for better code size insights.
How It Works
CodeSizer employs objdump to disassemble ELF files and addr2line to unwind inline call stacks. This process allows it to map code size back to specific functions, even when multiple inline functions are involved.
The resulting HTML report provides a clear visualization of the code size distribution across the call tree.