luke
/
iverilog
mirror of https://github.com/steveicarus/iverilog.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
iverilog/ivtest/gold/sv_queue_real_fail.gold

11 lines
790 B
Plaintext
Raw Normal View History

Consolidate unpacked array type elaboration There are currently two implementations for elaborating unpacked array types. One that is used when elaborating a signal with an unpacked array type and one that is used everywhere else using the elaborate_type() infrastructure. The elaborate_type() implementation is less complete and for example does not support bounded queue types. Consolidate both into a single implementation to reduce duplicated code and get consistent behavior. This for example makes sure that the maximum queue size is respected when used as a function return type. Nested data structures of arrays, dynamic arrays or queues are not yet supported. In the current implementation when encountering such a type an assert will be triggered and the application crashes. In the new implementation an error message will be printed without crashing the application. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2022-03-26 16:40:32 +01:00
./ivltests/sv_queue_real_fail.v:4: error: queue bound must be positive (-1).
./ivltests/sv_queue_real_fail.v:5: error: queue bound must be defined.
Add ivtest to the iverilog source tree By adding ivtest to the iverilog source tree, it is easier to keep the regression test synchronized with the source that is being tested. This should be especially helpful for PRs that add a new feature, and have a matching ivtest PR with the regression test for that feature.
2022-01-15 19:18:50 +01:00
./ivltests/sv_queue_real_fail.v:6: error: A reference to a wire or reg (`bound') is not allowed in a constant expression.
Consolidate unpacked array type elaboration There are currently two implementations for elaborating unpacked array types. One that is used when elaborating a signal with an unpacked array type and one that is used everywhere else using the elaborate_type() infrastructure. The elaborate_type() implementation is less complete and for example does not support bounded queue types. Consolidate both into a single implementation to reduce duplicated code and get consistent behavior. This for example makes sure that the maximum queue size is respected when used as a function return type. Nested data structures of arrays, dynamic arrays or queues are not yet supported. In the current implementation when encountering such a type an assert will be triggered and the application crashes. In the new implementation an error message will be printed without crashing the application. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
2022-03-26 16:40:32 +01:00
./ivltests/sv_queue_real_fail.v:6: error: queue bound must be constant.
Add ivtest to the iverilog source tree By adding ivtest to the iverilog source tree, it is easier to keep the regression test synchronized with the source that is being tested. This should be especially helpful for PRs that add a new feature, and have a matching ivtest PR with the regression test for that feature.
2022-01-15 19:18:50 +01:00
./ivltests/sv_queue_real_fail.v:9: error: size() method takes no arguments
./ivltests/sv_queue_real_fail.v:10: error: pop_front() method takes no arguments
./ivltests/sv_queue_real_fail.v:11: error: pop_back() method takes no arguments
./ivltests/sv_queue_real_fail.v:12: error: push_front() method requires a single argument.
./ivltests/sv_queue_real_fail.v:13: error: push_back() method requires a single argument.
9 error(s) during elaboration.