New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Evaluation of TACO compiler #299
Comments
This looks great to me. We'd be interfacing with cython? |
Is TACO similar to |
@dhirschfeld It's much better than that: It allows for sparse arrays in many different formats to be represented. And it allows for adding two separate tensors, which is something |
Thanks for the info! I was only vaguely aware of the project previously but it sounds like something I should keep an eye on... |
@daletovar I think pybind11 is the better choice here. |
After a thorough review of the options, I studied how the original TACO behaves. It emits C code, then calls the system compiler. I think we can probably do something similar: emit Python AST which can then be jitted with Numba. |
From all the examples I can see, the TACO compiler is good for
einsum
-type expressions, and any that involve tensor products, contractions and sums. I've posted about it here: tensor-compiler/taco#276The text was updated successfully, but these errors were encountered: