forked from OSchip/llvm-project
5988a3b7a0
Initially, the padding transformation and the related operation were only used to guarantee static shapes of subtensors in tiled operations. The transformation would not insert the padding operation if the shapes were already static, and the overall code generation would actively remove such "noop" pads. However, this transformation can be also used to pack data into smaller tensors and marshall them into faster memory, regardless of the size mismatches. In context of expert-driven transformation, we should assume that, if padding is requested, a potentially padded tensor must be always created. Update the transformation accordingly. To do this, introduce an optional `packing` attribute to the `pad_tensor` op that serves as an indication that the padding is an intentional choice (as opposed to side effect of type normalization) and should be left alone by cleanups. Reviewed By: nicolasvasilache Differential Revision: https://reviews.llvm.org/D110425 |
||
|---|---|---|
| .. | ||
| Analysis | ||
| Bindings/Python | ||
| CAPI | ||
| Conversion | ||
| Dialect | ||
| ExecutionEngine | ||
| IR | ||
| Interfaces | ||
| Parser | ||
| Pass | ||
| Reducer | ||
| Rewrite | ||
| Support | ||
| TableGen | ||
| Target | ||
| Tools | ||
| Transforms | ||
| Translation | ||
| CMakeLists.txt | ||