Conversation
Enable legacy BalarTestCPU trace replay checks for allocation/free and wide copies, including cudaFree replay support. Repair test decorators, fixture paths and optional toolchain setup without adding a new CPU or changing MMIO behavior.
This was referenced Sep 25, 2026
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.
Existing BalarTestCPU trace tests have broken skip decorators, stale fixture paths, and no cudaFree replay. Repair that setup and add basic allocation/free and wide-copy contracts using the existing driver. Isolate optional RISC-V/LLVM toolchain setup, shared statistic checks, and the direct-memory test topology.
This layer adds no DoorbellTestCPU and does not change MMIO runtime behavior.
Validation:
Incremental review PR in the contributor fork, based on
balar-1-wire-header. Upstream branch protection prevents feature-branch bases there. After the preceding layer lands upstream, submit this branch againstsstsimulator/sst-elements:devel; retain this fork PR as its incremental review record.Stack (review order):