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.
18 lines
1.1 KiB
Plaintext
18 lines
1.1 KiB
Plaintext
%Warning-BLKSEQ: t/t_lint_blksync_bad.v:24:16: Blocking assignment '=' in sequential logic process
|
|
: ... Suggest using delayed assignment '<='
|
|
24 | sync_blk = 1'b1;
|
|
| ^
|
|
... For warning description see https://verilator.org/warn/BLKSEQ?v=latest
|
|
... Use "/* verilator lint_off BLKSEQ */" and lint_on around source to disable this message.
|
|
%Warning-BLKSEQ: t/t_lint_blksync_bad.v:25:17: Blocking assignment '=' in sequential logic process
|
|
: ... Suggest using delayed assignment '<='
|
|
25 | sync_blk2 = 1'b1;
|
|
| ^
|
|
%Warning-COMBDLY: t/t_lint_blksync_bad.v:31:18: Non-blocking assignment '<=' in combinational logic process
|
|
: ... This will be executed as a blocking assignment '='!
|
|
31 | combo_nblk <= 1'b1;
|
|
| ^~
|
|
*** See https://verilator.org/warn/COMBDLY before disabling this,
|
|
else you may end up with different sim results.
|
|
%Error: Exiting due to
|