Wilson Snyder
Wilson Snyder
If the time is random then sounds there's at least two bugs here: 1. The functional problem of the bitstream 2. Why the behavior is non-determistic. We shouldn't depend in...
If you update to master you can now use `--aslr --debug` to force use of ASLR even when under debug.
The crash is fixed, however the specific streaming fails now at GCC compile time due to other issues, see test_regress/t/t_stream_type.py. Perhaps you'd be willing to look at a pull to...
I can see how this cleans things up a lot. It's also faster for lookup runtimes which is a major plus. >My preferred solution would have been to create a...
P.S. I can accept either merging the other pull where we don't change Emit and do strings at runtime, then improve this pull. Or, collapsing this into the other pull.
At a minimum IMHO we should warn the user that they have such code. It's not just about our behavior being different depending on scheduling, but that Verilator may make...
I suspect (without data) warning on your example won't cause many false warnings. It's at least worth a try, assuming we can identify them, as cross-simulator differences catch people a...
@YilouWang , @kozdra, @kbieganski?
@YilouWang if you have a chance or interest to add some flag or otherwise to help users debug constraints it would be helpful & see the note about `get-unsat-core`, thanks.
Enabling coverage - please check that all lines you added are covered, it's ok if there's uncovered branches you think are not critical.