steveicarus / ivtest Goto Github PK

Hello, there are some filenames in in tests, which seems to be incorrect.
Does the test runner reports these errors?

      # name present in .list file: real name present in FS
      {
            "br_ml201801012a": "br_ml20181012a",
            "br_ml201801012b": "br_ml20181012b",
            "br_ml201801012c": "br_ml20181012c",
            "br_ml201801012d": "br_ml20181012d",
            "struct_packe_write_read": "struct_packed_write_read",
            "struct_packe_write_read2": "struct_packed_write_read2",
            "sv_string_index": "string_index",
            "sv_timeunit_prec": "sv_timeunit_prec1",
            "sv_timeunit_prec_fail": "sv_timeunit_prec_fail1",
        }

Hello,

there is a comment between macro usage and it's parenthesis with arguments.
https://github.com/steveicarus/ivtest/blob/master/ivltests/macro_with_args.v#L46

Tools available on www.edaplayground.com/ (Synopsys VCS, Cadence Incisive, Aldec Riviera) does not support this syntax. From the LRM It seems to me that even if the comment is allowed on this place (I think it is not.) it would be removed later thus this should be an error as the macro should expect '(' and does have '/'. Or it is removed before parsing of macro, but then, there is a '\n' so it would also cause an error.

Hello,

there are may files with some form of extension in this test suite.
My problem is that I can not parse *.list files and detect it automatically.
Do you think we can add somehow this information?

I already collected all such a files:
https://github.com/Nic30/hdlConvertor/blob/sv2017/tests/test_icarus_verilog_testsuite.py#L193

Another thing is Icarus extension which allows to specify wire/reg before type id.
This appears in:

bool1, br974c, compare_bool_reg, constfunc8, pr1861212a, pr1861212c, pr1861212d, real8, size_cast2, struct_packed_array, struct_packed_array2, sv-2val-nets, enum_ports

Do you think it could be possible to remove this extension from some of the files (because some features from this files are not tested anywhere else)?

Does extensions which Icarus implements have some name or standard like IEEE1800-2017-iv?

What is the best source of informations about this extensions?

http://ecee.colorado.edu/~mathys/ecen2350/IntelSoftware/pdf/IEEE_Std1800-2017_8299595.pdf p 1163 event_trigger does support only hierarchical_event_identifier, that means the class scope ("::") is not allowed.

Functions are imported from package and then functions with same name are defined.

https://github.com/steveicarus/ivtest/blob/master/ivltests/sv_wildcard_import2.v#L57

I believe that this is not according to std., Vivado 2019.2 also see a syntax error.