Quacomm AI Engine Direct - Enable FCB feature to Qualcomm HTP

[quic-boyuc]

QNN Flexible Context Binary (FCB) multi-SoC HTP support

Adds offline FCB export for shipping one ExecuTorch artifact containing QNN HTP
contexts for multiple known Snapdragon SoCs. Requires QNN SDK >= 2.48.

User-facing API

• generate_qnn_executorch_compiler_spec() now accepts paired lists:
  soc_model=[...] and backend_options=[...].
• Supplying two or more distinct HTP targets enables FCB; scalar inputs retain
  the existing single-SoC behavior.
• Adds fcb_reference_weight_sharing=True by default. It shares referenced
  weights while host AOT appends target contexts to the FCB DLC.
• QnnQuantizer and make_quantizer() accept FCB target lists and validate
  against the least-capable requested HTP architecture.
• FCB rejects online preparation, non-HTP targets, mismatched target/options
  lists, duplicate SoCs, and DLBC when reference-weight sharing is enabled.

Architecture

• Extends the QNN compiler-spec schema with paired FCB target records and
  reference-weight-sharing configuration.
• Creates and caches one QNN manager per (backend type, SoC) during lowering.
• Validates operator support against every requested target.
• Reuses the same AOT op-wrapper graph sequentially for each target; graph
  registration state is reset after every compile, including failures.
• Adds Python adaptor operations to create an FCB DLC, append each compiled
  context, retrieve its bytes, and free the DLC.
• Uses QNN system DLC APIs at runtime to locate the compatible HTP context and
  deserialize its graph metadata.
• Adds compiler-spec and manager-lifecycle coverage plus FCB ResNet50 and
  multi-SoC weight-sharing examples.

Usage

Build the Android runner:

 # Build with QNN SDK >= 2.48.
./backends/qualcomm/scripts/build.sh


# Measure FCB and HTP weight-sharing combinations across multiple targets:

python -m examples.qualcomm.util_scripts.fcb_multi_soc_weight_sharing_demo \
  --soc_models SM8650 SM8750 SM8850 SM8550 \
  --devices adb-host-a:<serial-a> adb-host-b:<serial-b> \
  --build_folder build-android

#  Export and optionally validate a floating-point FCB artifact:

python -m examples.qualcomm.util_scripts.fcb_resnet50 \
  --soc_models SM8650 SM8750 \
  --devices <serial-on-SM8650> <serial-on-SM8750> \
  --build_folder build-android

# For devices attached to separate ADB servers, use host:serial values:

python -m examples.qualcomm.util_scripts.fcb_resnet50 \
  --soc_models SM8650 SM8750 \
  --devices adb-host-a:<serial-a> adb-host-b:<serial-b> \
  --build_folder build-android

# run FCB with quantized reset50   

python -m examples.qualcomm.util_scripts.fcb_resnet50_quantized \
     --soc_models SM8550 SM8850 SM8750 SM8650 \
     --dataset ~/executorch/imagenet-mini-val/val \
     --output_dir /tmp/qnn_fcb_resnet50_quantized \
     --devices adb-host-a:<serial-a> adb-host-b:<serial-b> \
     --build_folder build-android

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/22521

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

⚠️ 21 Awaiting Approval

As of commit 7de3f79 with merge base c8d5189 ():

AWAITING APPROVAL - The following workflows need approval before CI can run:

• Build Aarch64 Linux CUDA Wheels (gh)
• Build Aarch64 Linux Wheels (gh)
• Build documentation (gh)
• Build Linux CUDA Wheels (gh)
• Build Linux Wheels (gh)
• Build macOS Wheels (gh)
• Build Presets (gh)
• Build Windows Wheels (gh)
• Cadence Build & Test (gh)
• Lint (gh)
• periodic (gh)
• pull (gh)
• Test ARM Backend (gh)
• Test CoreML Backend (gh)
• Test Cortex-M Backend (gh)
• Test NXP Backend (gh)
• Test QNN Backend (gh)
• Test QNN Windows MSVC build (gh)
• Test Vulkan Backend (gh)
• Test WebGPU Backend (gh)
• Test XNNPACK Backend (gh)

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.