Wilson Snyder
Wilson Snyder
For v5 we should add a section to the documentation on how to upgrade, e.g. describe changes in delays, and how to change users' own main(), and use of --main...
@gezalore in #3419 suggests: >being able to register custom handlers for things like vl_fatal and friends by overriding VerilatedContext methods is also something I would favour in contrast to the...
Reminder that when develop-v5 is ready for beta we should update the wikipedia page to remove many of the described limitations.
I've created the develop-v5 branch. This will collect changes towards v5.002. This contains several major features including: * timed coroutines (#3363) * improved scheduling ~(#3329)~ (#3384) Please consider using this...
If you wish to receive infrequent announcements related to Verilator, such as release notices and other major news, please [Subscribe to Verilator announcements](https://github.com/verilator/verilator-announce).
@gezalore suggested some stronger node documentation, which is alternatively and probably best implemented as enforcement in e.g. V3Broken: - [ ] What nodes are legal in between each processing stage....
UVM and some real code uses recursive functions at runtime. Look into supporting them. I created/updated some t_func_recurse tests in master to try the primary cases.
When a function and variable has no explicit lifetime, Verilator defaults to automatic, but IEEE says to default to static. Verilator will likely change this to be compliant at some...
See https://chipsalliance.github.io/sv-tests-results/?v=verilator+8.3+class_test_7 This class extends into a package gives an incorrect syntax error: class Foo extends Package::Bar;
I found debugging #3207 that all parsed quoted strings are still handled as numeric types internally. It would be much cleaner and likely fix some bugs where a "var string"...