Open erang20 opened 9 months ago
Agree that type names can get pretty absurdly verbose. I have been noticing the same in some of the designs I have been involved in.
The current type name generation is actually according to what the SystemRDL spec defines (Section 5.1.1.4). I also extended the semantics for this to cover dynamic assignments.
I was actually thinking of addressing this in a similar way you suggested - to provide an option to generate shortened hashed type names. This is important since some languages that PeakRDL exports to may have a character limit on identifiers that is quite easy to reach with this behavior.
Since this is something that would be changed in the compiler, I will migrate this issue there.
RDL parameterized types translate to Node.type that contains the list of parameters and their values. For example:
Might be instantiated as a
Node
withtype_name
=some_regfile_PARAM_A_200_PARAM_B_300
The list of parameters might be very long in some cases, so it would be helpful to add an option (e.g.
max_node_type_param_lengh
to abbreviate a long parameters list to a 32 bit hash hex, e.g.some_regfile_2d8fa187
instead of a very long type name.