[mlir][tablegen] Correctly set Type constraint description #110939
Closed
+1
−1
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.
The common tablegen
Type
constraint was not honoring user specified description strings by unconditionally settingConstraint
's description to the empty string (this appears to be inadvertent fallout from https://reviews.llvm.org/D94133 in whichtypeDescription
was renamed todescription
, shadowing the existingdescription
field onConstraint
).This has the effect of making select quantized types (among other things) indistinguishable. For example, quantized types in the TFLite dialect are defined as:
Where
QuantizedType
is:Aside from
asTraitArgsStr
, signed/unsigned quantized types are indistinguishable at the parsed TD level notwithstanding thedescription
argument passed toType
. This fix forwards the user provided description to the underlyingConstraint
from whichType
inherits from.