v0.2: wrap the M7 codegen campaign - #11
Merged
Merged
Conversation
Declares the output-preserving phase of the optimization campaign complete and bumps the version (CMake project + TAP_RATIO_VERSION_*). Four levers landed, each measured by the instruction-count ratchet, outputs bit-identical throughout: the M7a harness itself, the M7b superblock walk, the M7c committed trip counts, and the M7d symmetry-halved tables. Cumulative vs the M7a baselines: M55 Q15 -59%/-60% and float -35%/-37%; M33 Q31 -26%/-27%, Q15 -15%/-16%; Hexagon Q15 -13%/-10%, Q31 -15%/-7%; table storage halved (economy Q15 up: 6.9 KiB). README and PLAN now state the deferral rationale for the remaining levers (multistage, minimum-phase, IIR pre-filter, FFT offline): each changes the output contract or serves a currently-unpressured need, so they wait for a consumer to pull them — a latency need pulls minimum-phase, a storage need pulls multistage, an MCU float consumer pulls the accumulation-contract discussion in DspTap. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ldeq57sBySx2nFTQsGcQB6
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
2 participants
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.
What
Declares the output-preserving phase of the M7 optimization campaign complete and bumps the version to 0.2.0 (CMake project +
TAP_RATIO_VERSION_*). Docs-and-version only — no engine changes, no baseline changes.What v0.2 contains (all previously merged, each measured by the ratchet, outputs bit-identical throughout):
dot_row_reversedkernel in DspTap).Cumulative vs the M7a baselines: M55 Q15 −59%/−60% and float −35%/−37%; M33 Q31 −26%/−27%, Q15 −15%/−16%; Hexagon Q15 −13%/−10%, Q31 −15%/−7%; table storage halved (economy Q15 up: 6.9 KiB).
README and PLAN now record the deferral rationale for the remaining §7 levers (multistage, minimum-phase, IIR pre-filter, FFT offline): each changes the output contract or serves a currently-unpressured need, so they wait for a consumer to pull them — a latency need pulls minimum-phase, a storage need pulls multistage, an MCU float consumer pulls the accumulation-contract discussion in DspTap.
Suggest tagging
v0.2.0on the merge commit.Verification
58/58 host suite green; version bump asserted nowhere (checked), so no test churn.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Ldeq57sBySx2nFTQsGcQB6
Generated by Claude Code