mirror of https://github.com/llvm/torch-mlir
4c557847bd
We were seeing some assertion failures after some checks around folders were tightened up in LLVM: https://github.com/llvm/llvm-project/pull/75887 . This PR essentially moves the logic that used to be applied at the LLVM level into the folder, which seems to be the suggested fix. I'm not sure if the IR that caused issues for us _should_ be valid? ``` %1 = torch.aten.detach %arg0 : !torch.tensor<[1],f32> -> !torch.tensor ``` A better fix might be to create a verifier ensuring the result of `aten.detach` has the same type as its operand. --------- Co-authored-by: aaron-stgeorge <aaron.stgeorge@getcruise.com> |
||
---|---|---|
.. | ||
GlobalizeObjectGraph | ||
adjust-calling-conventions.mlir | ||
canonicalize.mlir | ||
decompose-complex-ops-legal.mlir | ||
decompose-complex-ops.mlir | ||
drop-abstract-interp-calculations.mlir | ||
erase-module-initializer.mlir | ||
fuse-quantized-ops.mlir | ||
inline-global-slots-analysis.mlir | ||
inline-global-slots-transform.mlir | ||
invalid.mlir | ||
lower-to-backend-contract-error.mlir | ||
match-quantized-customs-ops.mlir | ||
maximize-value-semantics.mlir | ||
ops.mlir | ||
prepare-for-globalize-object-graph.mlir | ||
reduce-op-variants-error.mlir | ||
reduce-op-variants.mlir | ||
refine-public-return.mlir | ||
reify-dtype-calculations.mlir | ||
reify-shape-calculations.mlir | ||
simplify-dtype-calculations.mlir | ||
simplify-shape-calculations.mlir | ||
torch-function-to-torch-backend-pipeline.mlir | ||
verify-backend-contract-error.mlir | ||
verify-backend-contract-unimplemented-op.mlir |