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
%Error-BLKANDNBLK:xxx.sv: Unsupported: Blocked and non-blocking assignments to the same variable:structure_name.object_of_structure
As Documents suggest that we can't mix blocking and non-blocking assignments,but in System Verilog if i have one structure with 4 no. of elements and i am access various elements of structure by its object ,for few elements i am using blocking assignments and non-blocking assignments for remaining one which is permitted by System Verilog. But with verilator linting i am getting the error mentioned above.
Could you please help me in this????
Thank You,
Mehul Modhiya
The text was updated successfully, but these errors were encountered:
Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2017-03-14T13:40:42Z
Please use the forums for questions as opposed to bugs, thanks.
You can turn off this warning around that line, however your code might simulate differently. There's almost always an alternative way to code to avoid this problem, e.g. setting a flag in a always_comb, then testing it in two separate blocks.
Author Name: Mehul Modhiya
Original Redmine Issue: 1137 from https://www.veripool.org
Hello ,Everyone
While linting,i came across following errors
%Error-BLKANDNBLK:xxx.sv: Unsupported: Blocked and non-blocking assignments to the same variable:structure_name.object_of_structure
As Documents suggest that we can't mix blocking and non-blocking assignments,but in System Verilog if i have one structure with 4 no. of elements and i am access various elements of structure by its object ,for few elements i am using blocking assignments and non-blocking assignments for remaining one which is permitted by System Verilog. But with verilator linting i am getting the error mentioned above.
Could you please help me in this????
Thank You,
Mehul Modhiya
The text was updated successfully, but these errors were encountered: