mirror of https://github.com/llvm/torch-mlir
01290d134a
We were already hitting many cases where backends different in terms of the legal ops that they wanted. This caused unnecessary coupling between the backends. Examples: - https://github.com/llvm/torch-mlir/pull/1161 - https://github.com/llvm/torch-mlir/pull/862 This PR centralizes all compilation to go through `torch_mlir.compile` so that we can keep the logic centralized there. We should move these lists closer to each backend. Especially cases like https://github.com/llvm/torch-mlir/pull/862 where blocking a decomposition is necessary to avoid a crash emphasize that the set of decompositions is tightly coupled to the backend, and should be "controlled by the backend" and not something arbitrarily tweakable. Also: - Fix a small bug in the way we passed through the backendLegalOps option. - Add better error messages in `torch_mlir.compile` for import errors. |
||
---|---|---|
.. | ||
Torch | ||
TorchConversion |