Print perf result at the end of simulation #761
Merged
Conversation
This file contains 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
Avimitin
force-pushed
the
print-perf-final
branch
5 times, most recently
from
de79daf to
e33cbe5
Compare
Avimitin
force-pushed
the
print-perf-final
branch
from
db1875f to
ab27d9a
Compare
Avimitin
force-pushed
the
print-perf-final
branch
from
6c49aa3 to
0df2d8d
Compare
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.
Now t1/t1rocket will generate a
perf.jsonat the end of simulation, currently only contains the number of total cycle numbers.Here is the example of
nix build .#t1.t1rocket.ip.vcs-emu.cases.codegen.vadd_vv.emu-result, inresult/perf.json{ "total_cycles": 32444 }