-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Tutorial: deployment. An error occurred on arch x64 and cuda #8313
Comments
Can you try after installing taichi-nightly, remove the taichi package? (And regenerate the cmake files) |
After removing the taichi package, and I reinstalled taichi-nightly. There still occured segmentation fault in |
The Taichi AOT library shipped in the nightly-taichi does not have CUDA/x86 inside. You'll have to compile taichi from source code to enable C-API for CUDA/x86 or metal, etc. Luckily, there's an easy way to do that. The build system for https://github.com/taichi-dev/taichi-aot-demo has options to turn on CUDA/x86 backends. Just turn on "TI_WITH_CPU" and "TI_WITH_CUDA" when you do cmake. |
Thanks, I can compile taichi from source code! |
Description
I tried the tutorial (Doc Home>>Deployment>>Tutorial: Run Taichi programs in C++ applications). And I found it can successfully run on
vulkan
backend, then I changedapp.py
app.cpp
ti::Runtime runtime(TI_ARCH_VULKAN) -> ti::Runtime runtime(TI_ARCH_X64) or ti::Runtime runtime(TI_ARCH_CUDA)
After cmake compilation, ran
./build/TaichiAot
, there was a segmentation fault on bothx64
andcuda
arch.Then I noticed that "Before we start, it is recommended to install Taichi through taichi-nightly Python wheels using the following command. Be aware that there's no strong version compatibility enforced yet, so it's highly recommended to use the Taichi built from exactly the same commit." in tutorial. So I replaced taichi-nightly from 1.7.0.post20230804 to 1.6.0.post2023041. But I ran into a problem that I couldn't find
libtaichi_c_api.so
Development environment
hardware
software
The text was updated successfully, but these errors were encountered: