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

Consider unifying the LLVM offline cache and the AOT infrastructure #4565

Closed
k-ye opened this issue Mar 17, 2022 · 1 comment
Closed

Consider unifying the LLVM offline cache and the AOT infrastructure #4565

k-ye opened this issue Mar 17, 2022 · 1 comment
Assignees
Labels
feature request Suggest an idea on this project

Comments

@k-ye
Copy link
Member

k-ye commented Mar 17, 2022

We have made our first step towards the LLVM offline cache in #4500. Meanwhile, we are also developing our AOT infrastructure, tracked in #3642. There are lots of common features:

  • Save/load the compiled LLVM module
  • Maintain a mapping from a Taichi kernel identifier to the compiled LLVM mobile

Therefore, we should evaluate the feasibility of sharing code between these two directions.

cc @PGZXB @strongoier

@k-ye k-ye added the feature request Suggest an idea on this project label Mar 17, 2022
@PGZXB
Copy link
Contributor

PGZXB commented Mar 18, 2022

Thanks & Got it! I will evaluate the feasibility of sharing code between your two directions. At the proper time, maybe when starting AOT for llvm-backend, maybe after offline-cache infra is good enough, I will refactor some offline-cache code which can be reused by AOT for llvm-backend. And merge/unify them with AOT infrastructure.

@PGZXB PGZXB self-assigned this Sep 24, 2022
@PGZXB PGZXB closed this as completed Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Suggest an idea on this project
Projects
None yet
Development

No branches or pull requests

2 participants