forked from github/verilator
49c90ecbce
Some cases of warnings about the use of blocking and non-blocking assignments in combinational vs sequential processes were suppressed in a way that is inconsistent with the *actual* current execution model of Verilator. Turning these back on to, well, warn the user that these might cause unexpected results. V5 will clean these up, but until then err on the side of caution. Fixes #864.
12 lines
733 B
Plaintext
12 lines
733 B
Plaintext
%Warning-INITIALDLY: t/t_initial_dlyass.v:18:9: Non-blocking assignment '<=' in initial/final block
|
|
: ... This will be executed as a blocking assignment '='!
|
|
18 | a <= 22;
|
|
| ^~
|
|
... For warning description see https://verilator.org/warn/INITIALDLY?v=latest
|
|
... Use "/* verilator lint_off INITIALDLY */" and lint_on around source to disable this message.
|
|
%Warning-INITIALDLY: t/t_initial_dlyass.v:19:9: Non-blocking assignment '<=' in initial/final block
|
|
: ... This will be executed as a blocking assignment '='!
|
|
19 | b <= 33;
|
|
| ^~
|
|
%Error: Exiting due to
|