binary-size

Name: binary-size
Availability: InStock
Author: msabih

Analyze and reduce ExecuTorch binary size using CMake, nm, strings, and bloaty.

Updated Apr 30, 2026

Search Tags:#performance #optimization #build #bloat #binary-size #size-analysis #strip

Ready to run

npx skills add https://github.com/Msabih/executorch --skill binary-size-msabih

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: binary-size
Source: https://github.com/Msabih/executorch/tree/main/.claude/skills/binary-size
Command: npx skills add https://github.com/Msabih/executorch --skill binary-size-msabih

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze and reduce ExecuTorch binary size to enable deployment on constrained devices and to streamline build artifacts.

Core Features & Use Cases

Baseline measurement and comparison of stripped vs unstripped binaries using standard tooling such as nm, strings, and bloaty.
Identify large contributors in sections like .text and .rodata and apply size-focused compiler and linker settings.
Provide actionable guidance to reduce binary footprint for devices with tight storage and memory constraints.

Quick Start

Start from a clean build, then compare stripped and unstripped binaries to establish a baseline.

Frequently Asked Questions about binary-size

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I reduce ExecuTorch binary size for constrained devices?▼

Reduce ExecuTorch binary size by applying size-focused build workflows, such as using CMake with CMAKE_BUILD_TYPE=Release and EXECUTORCH_OPTIMIZE_SIZE=ON, to streamline artifacts for constrained device deployments.

What tools are used to analyze binary size contributors in ExecuTorch builds?▼

Analyze binary size contributors using standard utilities like nm, strings, and bloaty to pinpoint large sections such as .text and .rodata, enabling targeted optimization of the ExecuTorch binary footprint.

How do I establish a baseline measurement for binary footprint optimization?▼

Establish a baseline measurement for binary footprint optimization by starting from a clean build, then comparing stripped and unstripped binaries to identify initial size contributors before applying optimizations.

Can I use CMake build settings to optimize ExecuTorch binary size?▼

Yes, you can use CMake build settings to optimize ExecuTorch binary size by enforcing size-focused requirements, specifically configuring CMAKE_BUILD_TYPE=Release alongside EXECUTORCH_OPTIMIZE_SIZE=ON.

What is the best way to identify large contributors in .text and .rodata sections?▼

Identify large contributors in .text and .rodata sections by applying size-focused compiler and linker settings after using bloaty and nm utilities to analyze and pinpoint the exact size contributors within the binary.

When do I need to strip binaries for size-critical build workflows?▼

Strip binaries for size-critical build workflows when deploying to devices with tight storage and memory constraints, comparing stripped and unstripped outputs to measure the actual footprint reduction achieved.