This commit updates vector.contract documentation to clarify
the promotion behavior if operands and the result have different
bitwidths. It also adds a check to disable signed/unsigned integer
types and only allow signless integers.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
mlir/include/mlir/Dialect/Vector/IR/VectorOps.td | ||
---|---|---|
116 | Could we have an f16, f16 -> f32? |
mlir/include/mlir/Dialect/Vector/IR/VectorOps.td | ||
---|---|---|
116 | Yes I don't think the promotion behavior is specific to integer. What is specific to integers is whether we do signed or zero extend. |
Comment Actions
Address comments
mlir/include/mlir/Dialect/Vector/IR/VectorOps.td | ||
---|---|---|
116 | Good catch. Reworded accordingly. |
Could we have an f16, f16 -> f32?