Add regression test for task port range mismatch
Check that a range mismatch is detected for non-ANSI task ports when port direction and data type are declared separately. An error should be reported and no crash should occur. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
This commit is contained in:
parent
026d552be1
commit
a9c0469b2b
|
|
@ -0,0 +1,18 @@
|
|||
// Check that range mismatches between port direction and data type are detected
|
||||
// for task ports. An error should be reported and no crash should occur.
|
||||
|
||||
module test;
|
||||
|
||||
task t;
|
||||
input [1:0] x;
|
||||
reg [3:0] x;
|
||||
reg [3:0] y;
|
||||
y = x;
|
||||
$display("FAILED");
|
||||
endtask
|
||||
|
||||
initial begin
|
||||
t(4'b1001);
|
||||
end
|
||||
|
||||
endmodule
|
||||
|
|
@ -1610,6 +1610,7 @@ task_noop normal ivltests # Task with no contents.
|
|||
task_noop2 CO ivltests # Task *really* with no contents.
|
||||
task_omemw2 normal ivltests
|
||||
task_omemw3 CO ivltests # Pass bit selected from vector to task
|
||||
task_port_range_mismatch CE ivltests
|
||||
task_port_size normal ivltests # truncate task port connections
|
||||
task_scope normal ivltests
|
||||
tern1 normal ivltests # Finds problems with ?: using different sizes
|
||||
|
|
|
|||
Loading…
Reference in New Issue