Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

$pwd:

binary-size

Name: Binary Size
Author: pytorch

// Analyze and reduce ExecuTorch binary size. Use when investigating binary size, running size tests, or optimizing the runtime for size-constrained deployments.

Exécuter dans Manus

$ git log --oneline --stat

stars:4 652

forks:1 005

updated:7 mars 2026 à 01:33

SKILL.md

readonly

name	binary-size
description	Analyze and reduce ExecuTorch binary size. Use when investigating binary size, running size tests, or optimizing the runtime for size-constrained deployments.

Binary Size

Start from the `main` branch of executorch

Ask the user where the executorch repo is.

git checkout main && git pull

Build and measure baseline

conda activate executorch
bash test/build_size_test.sh
strip -o /tmp/size_test_stripped cmake-out/test/size_test
strip -o /tmp/size_test_all_ops_stripped cmake-out/test/size_test_all_ops
ls -la /tmp/size_test_stripped /tmp/size_test_all_ops_stripped

Produces two binaries:

cmake-out/test/size_test — ExecuTorch runtime without operator implementations
cmake-out/test/size_test_all_ops — ExecuTorch runtime with portable ops

Analyze with bloaty

bloaty cmake-out/test/size_test -d symbols -n 30   # by symbol
bloaty cmake-out/test/size_test -d sections        # by ELF section
bloaty <after> -- <before>                          # diff two builds
nm -S <binary> | sort -k2 -rn | head -30           # symbol sizes
strings <binary> | less                             # string literals in .rodata

Note: bloaty -d compileunits requires debug info (-g). The Release build does not include it.

Key build flags

Set by test/build_size_test.sh:

CMAKE_BUILD_TYPE=Release
EXECUTORCH_OPTIMIZE_SIZE=ON — enables -Os, -fno-exceptions, -fno-rtti, unwind table suppression
CXXFLAGS="-fno-exceptions -fno-rtti -Wall -Werror"

Constraints

Use CMake to build (not Buck)
C++17 minimum language standard
Must build on GCC 9 (CI uses executorch-ubuntu-22.04-gcc9-nopytorch) and Clang 12 — avoid compiler-specific flags or pragmas without version guards
Do not regress existing functionality — run tests for modified files
Do not change build flags in build_size_test.sh for size reductions
Do not increase latency in the core runtime

Where to look for size reductions

.text: look for large functions, template bloat, duplicate instantiations
.rodata: verbose error messages, format strings, embedded file paths (__FILE__)
.eh_frame: should already be suppressed when EXECUTORCH_OPTIMIZE_SIZE=ON
Static init functions (nm -S <binary> | grep GLOBAL__sub_I): use constexpr constructors to constant-initialize static arrays
Logging strings: ET_LOG_ENABLED=0 in Release eliminates format strings; ensure it propagates to consumers via PUBLIC compile definitions on cmake targets
Inline header functions: watch for compile-define mismatches between library and consumer TUs (e.g. ET_LOG_ENABLED set in library but not in consumer)

For each change

Create a branch: git checkout -b binary-size-<N>
Implement, rebuild, measure stripped sizes
Create a separate PR — one logical change per PR
Record results in binary-size-<N>.md:

Binary	This change (N vs N-1)	Cumulative (N vs main)
`size_test` (stripped)	-X	-Y
`size_test_all_ops` (stripped)	-X	-Y

Update the CI size threshold in .github/workflows/pull.yml if sizes decrease

related-skills.json

même dépôt

qualcomm.md

from "pytorch/executorch"

Build, test, or develop the QNN (Qualcomm AI Engine Direct) backend. Use when working on backends/qualcomm/, building QNN (use backends/qualcomm/scripts/build.sh), adding new ops or passes, running QNN delegate tests, or exporting models for Qualcomm HTP/GPU targets. Also exposes a Buck-vs-CMake parity workflow — invoke as `/qualcomm buck-fix`, `/qualcomm buck-cmake fix`, `/qualcomm buck-parity`, or any user request to fix `test-qnn-buck-build-linux` CI failures or check buck/cmake drift in backends/qualcomm/.

2026-05-204.7k

zephyr.md

from "pytorch/executorch"

Build and configure ExecuTorch as a Zephyr RTOS module for embedded boards. Use when setting up a Zephyr workspace with ET, adding board support (overlays, confs, memory layout), building with west, or debugging linker memory overflow.

2026-04-294.7k

executorch-kb.md

from "pytorch/executorch"

Search the ExecuTorch tribal knowledge base covering QNN, XNNPACK, Vulkan, CoreML, Arm, and Cadence backends, quantization recipes, export pitfalls, runtime errors, and SoC compatibility. Use when debugging ExecuTorch errors, choosing quantization configs, checking backend op support, or answering questions about Qualcomm HTP / Snapdragon / Apple Neural Engine behavior.

2026-04-214.7k

building.md

from "pytorch/executorch"

Build ExecuTorch from source — Python package, C++ runtime, runners, cross-compilation, and backend-specific builds. Use when compiling anything in the ExecuTorch repo, diagnosing build failures, or setting up platform-specific builds.

2026-03-114.7k

export.md

from "pytorch/executorch"

Export a PyTorch model to .pte format for ExecuTorch. Use when converting models, lowering to edge, or generating .pte files.

2026-02-194.7k

cortex-m.md

from "pytorch/executorch"

Build, test, or develop the Cortex-M (CMSIS-NN) backend. Use when working on backends/cortex_m/, running Cortex-M tests, or exporting models for Cortex-M targets.

2026-02-114.7k

package.json

"author": "pytorch"

"repository": "pytorch/executorch"

Ouvrir le dépôt GitHub Voir les dépôts du créateur

$ install --global

$ download --local

Exécuter dans Manus

$ useful --forSOC

Développeurs de logicielsProfessions informatiques et mathématiques15-1252L4

name	binary-size
description	Analyze and reduce ExecuTorch binary size. Use when investigating binary size, running size tests, or optimizing the runtime for size-constrained deployments.

Binary Size

Start from the `main` branch of executorch

Ask the user where the executorch repo is.

git checkout main && git pull

Build and measure baseline

conda activate executorch
bash test/build_size_test.sh
strip -o /tmp/size_test_stripped cmake-out/test/size_test
strip -o /tmp/size_test_all_ops_stripped cmake-out/test/size_test_all_ops
ls -la /tmp/size_test_stripped /tmp/size_test_all_ops_stripped

Produces two binaries:

cmake-out/test/size_test — ExecuTorch runtime without operator implementations
cmake-out/test/size_test_all_ops — ExecuTorch runtime with portable ops

Analyze with bloaty

bloaty cmake-out/test/size_test -d symbols -n 30   # by symbol
bloaty cmake-out/test/size_test -d sections        # by ELF section
bloaty <after> -- <before>                          # diff two builds
nm -S <binary> | sort -k2 -rn | head -30           # symbol sizes
strings <binary> | less                             # string literals in .rodata

Note: bloaty -d compileunits requires debug info (-g). The Release build does not include it.

Key build flags

Set by test/build_size_test.sh:

CMAKE_BUILD_TYPE=Release
EXECUTORCH_OPTIMIZE_SIZE=ON — enables -Os, -fno-exceptions, -fno-rtti, unwind table suppression
CXXFLAGS="-fno-exceptions -fno-rtti -Wall -Werror"

Constraints

Use CMake to build (not Buck)
C++17 minimum language standard
Must build on GCC 9 (CI uses executorch-ubuntu-22.04-gcc9-nopytorch) and Clang 12 — avoid compiler-specific flags or pragmas without version guards
Do not regress existing functionality — run tests for modified files
Do not change build flags in build_size_test.sh for size reductions
Do not increase latency in the core runtime

Where to look for size reductions

.text: look for large functions, template bloat, duplicate instantiations
.rodata: verbose error messages, format strings, embedded file paths (__FILE__)
.eh_frame: should already be suppressed when EXECUTORCH_OPTIMIZE_SIZE=ON
Static init functions (nm -S <binary> | grep GLOBAL__sub_I): use constexpr constructors to constant-initialize static arrays
Logging strings: ET_LOG_ENABLED=0 in Release eliminates format strings; ensure it propagates to consumers via PUBLIC compile definitions on cmake targets
Inline header functions: watch for compile-define mismatches between library and consumer TUs (e.g. ET_LOG_ENABLED set in library but not in consumer)

For each change

Create a branch: git checkout -b binary-size-<N>
Implement, rebuild, measure stripped sizes
Create a separate PR — one logical change per PR
Record results in binary-size-<N>.md:

Binary	This change (N vs N-1)	Cumulative (N vs main)
`size_test` (stripped)	-X	-Y
`size_test_all_ops` (stripped)	-X	-Y

Update the CI size threshold in .github/workflows/pull.yml if sizes decrease

binary-size

Binary Size

Start from the main branch of executorch

Build and measure baseline

Analyze with bloaty

Key build flags

Constraints

Where to look for size reductions

For each change

Plus depuis ce dépôt

Plus depuis ce dépôt

Binary Size

Start from the main branch of executorch

Build and measure baseline

Analyze with bloaty

Key build flags

Constraints

Where to look for size reductions

For each change

Start from the `main` branch of executorch

Start from the `main` branch of executorch