You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I observe that, the current firrtl.connect only checks the src width not larger than the dst width, but not vice versa. since in the firrtl parser logic we already define some the padding and truncate logic, we can make firrtl.connect be more strict, e.g. checking width exactly same to find width bug in the early phase.
The text was updated successfully, but these errors were encountered:
sequencer
changed the title
more strict connect semantic
[FIRRTL] more strict connect semantic
Jan 12, 2025
strictconnect has those semantics. connect is essentially dead through the pipeline and exists for parsing and fixing up the padding and truncation early on.
I observe that, the current
firrtl.connect
only checks the src width not larger than the dst width, but not vice versa. since in the firrtl parser logic we already define some the padding and truncate logic, we can make firrtl.connect be more strict, e.g. checking width exactly same to find width bug in the early phase.The text was updated successfully, but these errors were encountered: