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
Author Name: Lane Brooks
Original Redmine Issue: 43 from https://www.veripool.org
Original Date: 2008-11-12
Original Assignee: Wilson Snyder (@wsnyder)
I discovered in verilator that it is possible to select into a wire out side of its boundaries and the selection wraps. e.g.:
out10 and out32 come out equal. I am not sure what the verilog standard says, but I think I am used to this giving an error in other tools. I have attached a test that shows the behavior.
The text was updated successfully, but these errors were encountered:
Original Redmine Comment
Author Name: Wilson Snyder (@wsnyder)
Original Date: 2008-11-13T01:55:50Z
There was the t_select_bad_range test, but the difference and bug happens only when the MSB of the select range is binary all 1s and selects the entire width of the original signal. This causes the V3Width stage to optimize it before the warning sees it.
Author Name: Lane Brooks
Original Redmine Issue: 43 from https://www.veripool.org
Original Date: 2008-11-12
Original Assignee: Wilson Snyder (@wsnyder)
I discovered in verilator that it is possible to select into a wire out side of its boundaries and the selection wraps. e.g.:
wire [1:0] in;
wire [1:0] out32 = in[3:2];
wire [1:0] out10 = in[1:0];
out10 and out32 come out equal. I am not sure what the verilog standard says, but I think I am used to this giving an error in other tools. I have attached a test that shows the behavior.
The text was updated successfully, but these errors were encountered: