Open Thomasb81 opened 1 year ago
@Thomasb81, there is no effort (and bandwidth on my end) in the non-elaborated tree to compute the correct data type. Only in the elaborated tree. You or @hs-apotell are welcome to contribute the required changes in the non-elaborated tree.
Both cases presented here are identical in nature, only a placeholder type in the non-elaborated tree, and correct type in the elaborated tree
The uhdm elaborated tree is
On both ConsAssign, Lhs vpiActual return a
logic_net
, while it should probably belogic_var
.As
a
is declare as a variable, the linter should throw an error. See chapter 6.5 : Alternatively, variables can be written by one continuous assignment or one port.In non-elaborated model,
a
,b
and 'c' are capture has net. While by source code definition the tool should capture them as variable without elaboration step needed. Later in elaborated tree, element take their correct object type.See chapter 6.8 :