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
Original Redmine Comment
Author Name: Clifford Wolf (@cliffordwolf)
Original Date: 2014-05-05T11:04:36Z
Wilson Snyder wrote:
I fixed this as it is easy, but in general verilator is only a two state simulator with very limited X/Z handling, so would prefer focus on non-X/Z.
I already have a hack in place that ignores the verilator output bits that are set to X by the Yosys evaluator. Besides that it is hard to 'focus' on any specific kind of bug. For example I extracted this issue from the following test case: http://pastebin.com/UNWAmA0w (bug in y6 because p15 is undef). When generating test cases like that it is hard to avoid certain corner cases while at the same time trying to cover all the other corner cases.. ;)
Author Name: Clifford Wolf (@cliffordwolf)
Original Redmine Issue: 760 from https://www.veripool.org
Original Date: 2014-05-04
Original Assignee: Wilson Snyder (@wsnyder)
Verilator 4a58e85 creates the following error:
"%Error: Internal Error: ../V3Number.cpp:521: toUInt with 4-state 4'bxxxx"
The text was updated successfully, but these errors were encountered: