Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Verilator 4 vs. 5 #153

Open
schoeberl opened this issue Jul 30, 2024 · 3 comments
Open

Verilator 4 vs. 5 #153

schoeberl opened this issue Jul 30, 2024 · 3 comments

Comments

@schoeberl
Copy link
Member

Verilator 5 generates code that is not compatible with our test driver.
@schoeberl
Copy link
Member Author

Building Verilator 4.028 from source fixed the issue. The latest 4.x did also not work.

@schoeberl
Copy link
Member Author

We should use VPI instead of direct access to C variables.

@schoeberl
Copy link
Member Author

Or better use boring to access the PC.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@schoeberl