Add Spike-STF Support, Update Dockerfile, and Fix README Links #265
+216
−20
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
Jatin-exe
force-pushed
the
jatin/spike-stf-dockerfile
branch
2 times, most recently
from
aff36ac to
b1a5e8f
Compare
Jatin-exe
force-pushed
the
jatin/spike-stf-dockerfile
branch
from
b1a5e8f to
59cbef8
Compare
|
Why is force-push needed? |
|
I had to amend my commit message, which required me to force push |
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.
Building on PR #246, this PR adds support for generating baremetal STF traces on Spike.
Changes:
traces/README.md.ubuntu:22.04toubuntu:24.04for improved compatibility.stf_toolsas a dependency forspike-stf.These changes enable non-interactive execution of Spike-STF scripts in the Docker environment and support baremetal STF trace generation.