Skip to content

Add Z01X sim tool runtime/simtime support#182

Merged
AlexJones0 merged 4 commits intolowRISC:masterfrom
AlexJones0:z01x_time_parsing
Apr 16, 2026
Merged

Add Z01X sim tool runtime/simtime support#182
AlexJones0 merged 4 commits intolowRISC:masterfrom
AlexJones0:z01x_time_parsing

Conversation

@AlexJones0
Copy link
Copy Markdown
Contributor

The format used for parsing the runtime and simulation time that is reported differs during the run phase for this simulation tool. Add the minimal relevant (somewhat fragile) logic to parse these values out so that they display correctly.

Also resolve some other miscellaneous cleanup surrounding the sim tools - see the commit messages for more information.

The `SyntaxError` is meant for use by Python's parser. Though we are
doing our own parsing logic here, it is typically used to suggest an
error in some given Python source code, not a file in general.

Signed-off-by: Alex Jones <alex.jones@lowrisc.org>
Remove stale arguments and add missing information.

Signed-off-by: Alex Jones <alex.jones@lowrisc.org>
Get Z01X closer to existing sim tools (xcelium and VCS) by implementing
log runtime and simtime parsing for DVSim to report.

Signed-off-by: Alex Jones <alex.jones@lowrisc.org>
Building z01x is logged with the same output as VCS (unlike running it)
- so if we are not running explicitly, just defer to how the VCS tool
parses the logs. To be able to tell what type of test we are running,
expose the job specification to the sim tool when retrieving runtime
information, as the underlying (sub)tools might be different for each
phase.

Signed-off-by: Alex Jones <alex.jones@lowrisc.org>
Copy link
Copy Markdown
Collaborator

@machshev machshev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @AlexJones0

@AlexJones0 AlexJones0 added this pull request to the merge queue Apr 16, 2026
Merged via the queue into lowRISC:master with commit b8d553c Apr 16, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants