Repository navigation
Add Detroit regression witnesses and qualify the CPU candidate - #23
Merged
Merged
Conversation
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.
Mainline's general logical handler already supports Detroit's EORI postincrement cases. Add ten sparse-bus regression witnesses and prepare the frozen, unpublished
1.5.4-qualified-dev.1candidate without adding a duplicate production execution path.The witnesses verify results, CCR, exact PC, register preservation, access sizes, guard memory and A7 byte stride. Production CPU execution code is unchanged.
Validation:
The CPU DLL was verified byte-identical across CPU tests, the frozen NuGet package and consumer outputs. Detailed evidence and hashes are in
docs/COPPER68K_QUALIFIED_DETROIT_INTEGRATION_2026-10-11.mdand its JSON record.Five deferred qualification areas remain visible and the roadmap is not marked complete. This does not add hardware, external-reference or throughput qualification. No NuGet publication is included; this draft preserves the separately authorized release boundary.