⚠ This page is served via a proxy. Original site: https://github.com
This service does not collect credentials or authentication data.
Skip to content

Cortex-M backend: Introduce QuantizerReporter#17277

Open
AdrianLundell wants to merge 1 commit intopytorch:mainfrom
AdrianLundell:change-1189349
Open

Cortex-M backend: Introduce QuantizerReporter#17277
AdrianLundell wants to merge 1 commit intopytorch:mainfrom
AdrianLundell:change-1189349

Conversation

@AdrianLundell
Copy link
Collaborator

@AdrianLundell AdrianLundell commented Feb 6, 2026

The QuantizerReporter logs how a graph is annotated.

Basic useage:

  1. Implement the QuantizerReporterUser API for all quantizers intending to use the reporter.
  2. Instantiate the QuantizerReporter with a list of quantizers to be reported.
  3. After annotation, log the report using QuantizerReporter.log_quantizer_report(model).

Logs a summary report at INFO level, and a detailed node-per-node report at DEBUG level. See the added test for example output.

cc @freddan80 @per @zingo @oscarandersson8218 @digantdesai

The QuantizerReporter logs how a graph is annotated.

Basic useage:
1. Implement the QuantizerReporterUser API for all quantizers
intending to use the reporter.
2. Instantiate the QuantizerReporter with a list of quantizers
to be reported.
3. After annotation, log the report using
QuantizerReporter.log_quantizer_report(model).

Logs a summary report at INFO level, and a detailed node-per-node
report at DEBUG level. See the added test for example output.

Signed-off-by: Adrian Lundell <adrian.lundell@arm.com>
Change-Id: I8865a15fe83211351e8913f322c5707a81adfbf9
@AdrianLundell AdrianLundell added partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm release notes: none Do not include this in the release notes labels Feb 6, 2026
@pytorch-bot
Copy link

pytorch-bot bot commented Feb 6, 2026

🔗 Helpful Links

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

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

❌ 1 Awaiting Approval, 5 New Failures, 1 Unrelated Failure

As of commit 6b856f6 with merge base 03f066a (image):

AWAITING APPROVAL - The following workflow needs approval before CI can run:

NEW FAILURES - The following jobs have failed:

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

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

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Feb 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. partner: arm For backend delegation, kernels, demo, etc. from the 3rd-party partner, Arm release notes: none Do not include this in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant