-
Notifications
You must be signed in to change notification settings - Fork 653
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump to Verilator v5.022 #1800
Bump to Verilator v5.022 #1800
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was there any particular motivation for this bump?
Running |
Ah nice, Vikram was running into this |
@abejgonzalez Could you check on the CI? I'm able to run |
The |
I think you just have to manually delete '/scratch/buildbot/actions-runner-7/_work/chipyard/chipyard/software/firemarshal/disk-mount` off the build machines |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Pending CI passing.
can you make another release with this fix? latest v1.11 is still on 5.20 which is broken... or maybe update the documentation. |
Note that 5.022 has a major bug in |
Related PRs / Issues:
Type of change:
Impact:
Contributor Checklist:
main
as the base branch?changelog:<topic>
label?changelog:
label?.conda-lock.yml
file if you updated the conda requirements file?Please Backport
?Verilator v5.020 has a bug when building a debug simulator (verilator/verilator#4860). Bumping the Verilator version resolves this issue.