-
Notifications
You must be signed in to change notification settings - Fork 496
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
Unclear how to do a "really clean" build #1293
Comments
If we run the Release build script we are exposed to:
That said I think we can fix some of these docker issues by running them as the |
qedawkins
pushed a commit
to nod-ai/torch-mlir
that referenced
this issue
Oct 3, 2022
Signed-off-by: Whitney Tsang <whitneyt@ca.ibm.com>
qedawkins
pushed a commit
to nod-ai/torch-mlir
that referenced
this issue
Oct 3, 2022
The modification to use the builder based interface to generate Krnl loop is completed (llvm#1250, llvm#1283, llvm#1285, llvm#1292, llvm#1293, llvm#1303, llvm#1308, llvm#1314, llvm#1316, llvm#1317, llvm#1326, llvm#1403), and BuildKrnlLoop is no longer needed. Signed-off-by: Whitney Tsang whitneyt@ca.ibm.com
Development.md now has instructions: https://github.com/llvm/torch-mlir/blob/main/docs/development.md#cleaning-up |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I noticed that with source build of pytorch we end up caching some artifacts in build_tools/python_deploy (I think?). Can we make sure that we put all built artifacts in the build dir or have really clear docs about everything that gets built and how to clean it?
The text was updated successfully, but these errors were encountered: