Skip to content

Change OpenTitan to no-assert to override Verilator's change-of-default #5

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

Closed
wants to merge 1 commit into from

Conversation

wsnyder
Copy link
Member

@wsnyder wsnyder commented Jul 9, 2025

Verilator now has --assert the default, so get back the OpenTitan loss due to this.

@gezalore
Copy link
Member

gezalore commented Jul 9, 2025

Have you investigated why --assert causes the drop? as there are no active assert/assume statements in the OpenTitan code (all are ifdefed out), I presume it is because of all the unique case statements?

Note Vortex has a drop which I suspect is due to the same. (It also had a broken assertion which caused some run failures. I fixed that I have fixed here 033e7ef.)

I'm leaning towards keeping the new default if the effect is well understood (and maybe improve speed later), or at least all designs should use either --assert or --no-assert.

@wsnyder
Copy link
Member Author

wsnyder commented Jul 9, 2025

Ok, let's keep --assert. I haven't debugger the drop, but agree suspect case related.

@wsnyder wsnyder closed this Jul 9, 2025
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