Conversation
Owner
Author
|
Superseded by the later merged end-to-end Android and release-acceptance PRs; the baseline-versus-fused preprocessing functionality is already present in main. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Measurement boundaries
Preprocessing is measured separately from the fused preprocess-plus-reference-inference cold/warm timings. This remains the deterministic reference backend, not QNN/NPU evidence, and power remains unmeasured.
Verification
Bash syntax and diff checks pass locally. CMake is unavailable on the Mac, so GitHub CI must compile/test native and Android targets and pass 16 KiB alignment checks before merge.