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
I am using slang and VCS to analyze syntacoreRISC V kernel and slang errors on multiple drivers of the static local function (which called in both always_ff blocks) variable tmp assignment during call at first_always_ff_call and second_always_ff_call but VCS not.
IEEE 1800-2017SystemVerilog LRM says that:
The always_ff procedure imposes the restriction that it contains one and only one event control and no
blocking timing controls. Variables on the left-hand side of assignments within an always_ff procedure,
including variables from the contents of a called function, shall not be written to by any other process.
Software tools should perform additional checks to warn if the behavior within an always_ff procedure
does not represent sequential logic
The standard says nothing about conditions on drivers inside always_ff, it simply prohibits them.
Does that code written correct apply to IEEE 1800-2017SystemVerilog LRM?
The text was updated successfully, but these errors were encountered:
likeamahoney
changed the title
always_ff procedure assignment at scr1_memory_tb_ahb.sv
always_ff multiple procedure assignment at scr1_memory_tb_ahb.sv
Mar 2, 2024
likeamahoney
changed the title
always_ff multiple procedure assignment at scr1_memory_tb_ahb.sv
[question][help wanted] always_ff multiple procedure assignment at scr1_memory_tb_ahb.sv
Mar 2, 2024
I am using
slang
andVCS
to analyzesyntacore
RISC V
kernel andslang
errors on multiple drivers of thestatic
local function (which called in bothalways_ff
blocks) variable tmp assignment during call at first_always_ff_call and second_always_ff_call butVCS
not.IEEE 1800-2017
SystemVerilog
LRM says that:The standard says nothing about conditions on drivers inside
always_ff
, it simply prohibits them.Does that code written correct apply to
IEEE 1800-2017
SystemVerilog
LRM?The text was updated successfully, but these errors were encountered: