You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following from the discussion in the fork from KU Leuven. I would like to have support for Verilator 5. Verilator 5 has better performance, support for timing constructs and support for assertions. It would also allow projects using the snitch cluster to use verilator 5. I think in general it would be useful to support more recent versions of tools, as this makes the upgrading process later down the line a lot easier (make small steps instead of big ones).
Upgrading to verilator 5 would involve the following steps:
Add the -no-timing flag to the current tests, which disables the new timing features in verilator 5
Add verilated_threads.o to the verilator build targets OR compile both the systemverilog and cpp sources using verilator, so verilator can manage which verilator files should be included
If you have any questions or comments, please let me know!
The text was updated successfully, but these errors were encountered:
Following from the discussion in the fork from KU Leuven. I would like to have support for Verilator 5. Verilator 5 has better performance, support for timing constructs and support for assertions. It would also allow projects using the snitch cluster to use verilator 5. I think in general it would be useful to support more recent versions of tools, as this makes the upgrading process later down the line a lot easier (make small steps instead of big ones).
Upgrading to verilator 5 would involve the following steps:
-no-timing
flag to the current tests, which disables the new timing features in verilator 5verilated_threads.o
to the verilator build targets OR compile both the systemverilog and cpp sources using verilator, so verilator can manage which verilator files should be includedIf you have any questions or comments, please let me know!
The text was updated successfully, but these errors were encountered: