llvm
/
torch-mlir
mirror of https://github.com/llvm/torch-mlir
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
1,729 Commits
47 Branches
1195 Tags
77 MiB
Commit Graph

5 Commits (d849cbad14730c2af35ced046df03be2fe9a87eb)

Author SHA1 Message Date
Sean Silva cc468d2d16 [cleanup] Be consistent about apostrophe 2022-11-10 07:42:15 -08:00
Sean Silva 64914603fa [torch_mlir.compile] Add support for multiple exported methods 
For AoT deployments models often have multiple exported methods.
This patch enables something like this:

```
class TwoMethodsModule(torch.nn.Module):
    def sin(self, x):
        return torch.ops.aten.sin(x)

    def cos(self, x):
        return torch.ops.aten.cos(x)

example_args = torch_mlir.ExampleArgs()
example_args.add_method("sin", torch.ones(2, 3))
example_args.add_method("cos", torch.ones(2, 4))
print(torch_mlir.compile(TwoMethodsModule(), example_args))
```

In the
[long-term](https://github.com/llvm/torch-mlir/blob/main/docs/long_term_roadmap.md#tools-for-advanced-aot-deployments)
we will need to reconcile this with our story for stateful models and the
backend contract being purely functional. For now, this provides some basic
infra that seems harmless. Arguably, we could tighten up the backend contract
even more to only allow a single compiled function which would prohibit this or
require building out a layer above.

Fixes #1557
 2022-11-10 02:10:22 -08:00
Daniel Ellis 4d47f1671a Reject dictionary inputs when tracing. 
The underlying error message was misleading.  See https://github.com/llvm/torch-mlir/issues/1425
 2022-09-30 16:02:35 -04:00
Sean Silva 31727f81d8 torch_mlir.compile: Allow ignoring traced shapes 
In some cases, users know that a traced graph is valid for a wider set
of shapes than they originally traced it with. Provide an option for
users to ignore the shapes in the traced graph when they know it is
legal.

Fixes #997
 2022-08-04 10:18:34 -07:00
Sean Silva ccc858f531 torch_mlir.compile: Fix API footgun 
use_tracing=True was behaving unexpectedly because the handling of
single arguments was happening after the torch.jit.trace call.

This also fixes the check to specifically test for a torch.Tensor or
TensorPlaceholder so that both lists and tuples would be correctly
handled.
 2022-06-05 18:10:07 -07:00