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

Add an untyped ArrayFire backend and benchmark it vs hmatrix #71

Open
Mikolaj opened this issue Oct 6, 2022 · 0 comments
Open

Add an untyped ArrayFire backend and benchmark it vs hmatrix #71

Mikolaj opened this issue Oct 6, 2022 · 0 comments
Labels
help wanted Extra attention is needed

Comments

@Mikolaj
Copy link
Owner

Mikolaj commented Oct 6, 2022

See #43. The idea is to map the ArrayFire arrays to untyped orthotope tensors in the Domains and related types. For this early experiment, we can leave optimizers unchanged and using hmatrix in each case.

The benchmark would have variants using sequential hmatrix and parallel hmatrix (via flags read by the C/Fortran libraries) on CPU would also run the same ArrayFire-based code on GPU.

Eventually we'd prefer our code to be backend-independent, but that would require a general enough common representation. This may turn out to be ArrayFire, MLIR or something custom and higher level than MLIR. For now let's experiment with backends explicitly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant