Closed QuantamHD closed 1 year ago
unsupported_typespec
comes from Surelog, so I've created issue there: https://github.com/chipsalliance/Surelog/issues/3630.
When top_flag_t
is declared in package instead of file level, Surelog reports it correctly, so it might be temporary workaround.
Original issue (unsupported_typespec
) is now fixed with newest Surelog, but now this test fails with different union members size that is tracked in: https://github.com/chipsalliance/yosys-f4pga-plugins/issues/503.
I've also created PR that adds this test to UHDM-integration-tests
: https://github.com/chipsalliance/UHDM-integration-tests/pull/731
Surelog added missing ranges when union is defined in package, but it still lacks information about them, when union is defined on file level. I've created issue in Surelog to fix this: https://github.com/chipsalliance/Surelog/issues/3654
This issue should also be fixed when using submodules after: https://github.com/antmicro/yosys-systemverilog/pull/1721
@QuantamHD @grotival could you please check if this works for you?
verified: everything is good. Thanks for the fix!
When running the following example we get the error
hardware/tools/open_road/surelog_testcases/struct.sv:27 Encountered unhandled typespec in process_typespec_member: 'foo_flags::common_flags_t' of type 'unsupported_typespec'
@kamilrakoczy Can you take a look for the Google related work.
cc @hzeller