-
Notifications
You must be signed in to change notification settings - Fork 15
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
Verilator lint fixes #19
Conversation
553720c
to
017ac05
Compare
This comment was marked as outdated.
This comment was marked as outdated.
017ac05
to
663dfcc
Compare
@microsoft-github-policy-service agree company="lowRISC" |
This comment was marked as outdated.
This comment was marked as outdated.
Thanks - sorry for the delayed response and I will look into it. I haven't been ignoring this but just a little swamped recently. We may have to do a manual merge this time since there are a few more updates on my side as well. |
This comment was marked as resolved.
This comment was marked as resolved.
22e94c2
to
a038a80
Compare
Verilator 4.210 does not support this type of array assigment so I've split it up to improve compatibility.
This solves Verilator width lint warnings.
a038a80
to
3290c74
Compare
I've removed two commits from this PR because of recent changes and to revert a change in behavior. This should now be ready for review. |
This PR fixes various problems picked up by browsing Verilator lint warnings. Please have a look at the individual commit messages for details of why the changes were made.