[FIRRTL][IMCP] Mark DPI calls as overdefined #8515
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mark
DPICallIntrinsicOp
s as over-defined in the FIRRTL IMConstProp pass to prevent connections to the call's result from being removed.Running this Chisel 7 snippet through
firtool
incorrectly produces
The DPI call intrinsics ale initialized as
Unknown
in the constant propagation lattice and due to their cyclic dependency, this never gets resolved. This eventually leads to the connection to thebar
wire being removedIMConstProp.cpp:1091
:Initializing the call results to
Overdefined
prevents this.I'm not familiar with this pass, but the
!isOverdefined(fieldRef)
check before deleting a connection looks a bit too optimistic to me. Is it an invariant at this point that every value is known to be either constant or overdefined? If so, this should probably get anassert
, right?