mirror of
https://github.com/lowRISC/ibex.git
synced 2025-04-24 22:07:43 -04:00
As discussed in issue #845, this tells VCS to wait for signals to settle in combinatorial blocks before checking uniqueness in constructs like unique case. Otherwise things like this can cause spurious warnings: always_comb b = ~in; always_comb c = in; always_comb begin unique case (1'b1) b: x = 1; c: x = 0; default: x = 0; // not that it matters, but this won't happen endcase end For example, on a falling edge of the in signal, if the processes are executed in the order 1, 3, 2 then the unique case block will appear to see both b and c true at the same time. |
||
---|---|---|
.. | ||
cs_registers | ||
riscv_compliance | ||
uvm | ||
verilator |