Skip to content
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

Standardizing Weld's IR code #516

Open
espetro opened this issue Dec 23, 2020 · 1 comment
Open

Standardizing Weld's IR code #516

espetro opened this issue Dec 23, 2020 · 1 comment

Comments

@espetro
Copy link

espetro commented Dec 23, 2020

Hi there,

I have a growing interest in this project and, as it's asked in other issues, I don't know if this project is still active or not. That being said, I've seen that the current implementation seizes the power of Rust, but what about using IR frameworks such as MLIR ?

@sppalkia
Copy link
Collaborator

Good question, MLIR is indeed interesting for Weld's use case. We haven't tried it before (and we're currently not working on Weld actively), but if someone were to take a stab at using it as Weld's backend, I'd be happy to provide reviews/suggestions.

The Weld frontend currently doesn't have too many optimizations around n-ary arrays (and in fact, does not yet support a tensor type since the primary use case for now has been more 'slice and dice' ETL-like workloads in libraries like Pandas), so that may be a good starting point: if the frontend is capable of applying some interesting optimizations over tensors, the availability of these types in the backend IR will become much more compelling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants