tree c30e92075770360cd7eb9f668cbc9bb5d5d6b940
parent e718fa3d43455faf3c8546f406e8443961c87add
author Stella Laurenzo <laurenzo@google.com> 1659302172 -0700
committer GitHub <noreply@github.com> 1659302172 -0700
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJi5vEcCRBK7hj4Ov3rIwAAnqUIAFihg6bEzIAwIgLf/x7GxnSH
 yaKHTV14Ori3wVNJurccpJyeaYwyHj50tEXnk3+oQovScaQt2E3oK79uK9rQg7ZP
 3MYQuzvtsM4sEmtSAs/lbCFjhfQ1U98tr0OqS1aQ4Q1WYPNnS4DiIwdeCxO1QyQj
 zR+1lDusy24UlOeII5jxAnSuUSZrIIfj41vvm/Ose4CRbYSMjSirNYxpINXoaeco
 LXJjbH7aIFRvnxTkVDvr6Iyddb+EMfLygUDFs6OxMFXs/iaEN0flbdPzGxOatWJW
 xmz6kpt0bIF1O91AwWcfog8tBR4T2o6dNHnnmT3A8Tax7YDTvAXVhXaWVRD7a4E=
 =54ZF
 -----END PGP SIGNATURE-----
 

Add low level interface for defining VM modules in Python. (#9964)

* Add low level interface for defining VM modules in Python.

Inspired by #9947, which shows how to extend IREE with custom C modules,
I just had to do the plumbing to also allow extension from Python. Usual
caveats apply about Python being a terrible thing to implement real
things in, but there is no escaping how easy it is -- in my experience,
people will start by defining simple Python modules and then if we line
that up seamlessly with how you do it in C, it creates a good glide
path to progressively enhance.

This is just the start. Specifically, it does not yet:

* High level sugar: this is a low level interface that is aligned with
  the VM. It is TBD to add some nice-feeling decorators and such.
* Custom types not yet plugged through, but I expect that this could be
  pretty nicely done and interop well with Python.
* There's likely a nice story for integrating with the compiler side,
  but it needs more thought (i.e. custom ops directly from Python, etc)
  to make automatic. Also involves the usual grind of handling the ABI
  type grid, which I don't have time for today.