39589add22
If mhlo.reshape is not purely collapsing some consecutive operand dimensions into result dimensions, we will generate two linalg reshape op for it: the first one collapses all operand dimensions into one dimension, and the second one expands it to all result dimensions. For this case, the number of collapsed/expanded dimensions should be coming strictly from the operand/result. It is different from the case where we can generate one linalg reshape. For that case, the reassociation map should have rank equal to the largest among operand/result shape. PiperOrigin-RevId: 354293826 |
||
|---|---|---|
| .. | ||
| IR | ||
| transforms | ||
| CMakeLists.txt | ||