And you're just making the case against Verilog.
-
-
Replying to @M_Labs_Ltd @oe1cxw
verilog has many flaws, but precisely because of that, a new HDL should hide these flaws from the user, not expose them
1 reply 2 retweets 3 likes -
Replying to @OlofKindgren @oe1cxw
Just don't use poor Verilog simulators.
1 reply 0 retweets 0 likes -
Replying to @M_Labs_Ltd @OlofKindgren
Just don't generate Verilog code that only works with simulators that provide special functionality above and beyond the language spec. :)
3 replies 2 retweets 6 likes -
Replying to @oe1cxw @OlofKindgren
And synthesizers must already implement something like that. Is it actually not in the Verilog spec? Then the spec should be fixed.
2 replies 0 retweets 0 likes -
Replying to @M_Labs_Ltd @OlofKindgren
There is certainly nothing in the Vlog std about detecting and breaking loops. Nor should there be. 1/6
1 reply 0 retweets 0 likes -
And I seriously doubt that any tool does anything like that. Much more likely: Your code loops if events are 2/6
1 reply 0 retweets 0 likes -
popped from the active queue in one particular order, and doesn't loop with another order. But the spec says 3/6
1 reply 0 retweets 0 likes -
that a simulator can pop events from the active queue in any order it wants. So this just means that your 4/6
1 reply 0 retweets 0 likes -
code randomly works with some simulators or simulator versions and randomly breaks on others. If this happens 5/6
1 reply 0 retweets 0 likes
this simply means your code is broken and should be fixed. It does not mean one sim is "better" than another. 6/6
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.