-
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
[LLVM] Add missing pre-processor macro when LLVM is disabled #3702
[LLVM] Add missing pre-processor macro when LLVM is disabled #3702
Conversation
✔️ Deploy Preview for jovial-fermat-aa59dc canceled. 🔨 Explore the source changes: 70d765b 🔍 Inspect the deploy log: https://app.netlify.com/sites/jovial-fermat-aa59dc/deploys/61aad5662b22b40007606319 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm, thanks!
@AmesingFlank Thanks to your feedback, I just pushed the changes related to the other PR I closed to this one as they are all related to LLVM. |
taichi/backends/device.cpp
Outdated
if (dynamic_cast<vulkan::VulkanDevice *>(dst.device) && | ||
dynamic_cast<cpu::CpuDevice *>(src.device)) { | ||
// TODO: support direct copy if dst itself supports host write. | ||
return Device::MemcpyCapability::RequiresStagingBuffer; | ||
} | ||
#if TI_WITH_CUDA | ||
#elif TI_WITH_CUDA |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#elif TI_WITH_CUDA | |
#if TI_WITH_CUDA |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is the reason the tests are failing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That makes sense, not sure why I used a #elif, I missed this use case in my testing
Some components were still referencing LLVM with TI_WITH_LLVM set to false triggering a build failure.
Some components were still referencing LLVM with TI_WITH_LLVM set to
false triggering a build failure.
Related issue = #3679