Bloat Bdscr !new! May 2026

Always audit your linker scripts and descriptor data structures – especially when porting code across different flash architectures or toolchains.

objcopy --remove-section=.bdscr firmware.elf stripped.elf Scenario: A Zigbee IoT hub firmware had a .bdscr section of 64KB, but only 2KB was actually used. bloat bdscr

gcc -DNDEBUG -ffunction-sections -fdata-sections ... ld --gc-sections -o output.elf input.o Or manually strip after linking: Always audit your linker scripts and descriptor data

5.1. Linker Script Optimization Replace: bloat bdscr

bdscr_t blocks[256]; // 256 * 32 bytes = 8KB Use:

bloaty -d sections firmware.elf | grep bdscr Bloat in bdscr is a subtle but impactful inefficiency in embedded and low-level software. It stems from over-alignment, static allocation, and leftover debug structures. Detecting it requires basic binary inspection tools; fixing it yields measurable gains in size, speed, and maintainability.