-
Notifications
You must be signed in to change notification settings - Fork 768
[SYCL] Using a lambda in a kernel causes a linker crash #2376
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
Comments
@AlexeySachkov , @AlexeySotkin FYI |
I bet that FE optimizations changed the IR in a way that we cannot translate it anymore. Lack of non-constant memove support is a known issue of the translator, @AlexeySotkin, could you please take a look as you already have a PR for non-constant memset in flight? |
Any update on this? The hipSYCL unit tests also trigger this ICE when compiling with hipSYCL's new SPIR-V backend (which basically uses the clang SYCL frontend with hipSYCL header files and runtime) EDIT: In my case the error is slightly different, complaining about the size of the memcpy:
|
I've tried test case from @krasznaa with the latest compiler sources and it fails with an assertion from clang FE. @elizabethandrews , @premanandrao , @AaronBallman , FYI.
|
When trying to reduce the example, I noticed that something strange is happening. I had gotten it down to:
I could still reproduce the failed assertion with that. Notice how the |
FYI: the translator's problem with llvm.memmove of non-constant length should be fixed now KhronosGroup/SPIRV-LLVM-Translator#1060 , the fix will come here with one of the next pull downs, it doesn't fix the front-end assertion fail though. |
Enable adapter tests to run on all discovered adapters.
Dear All,
Similar to #2353 (but definitely not the same thing), I now ran into a linking issue while using lambdas. 😦
Take the following code:
With a few-day-old version of the compiler, I get the following while trying to build it:
I may be wrong, but I'm 99% sure that code like this did work in the past... 😕 Do you have any ideas on what's going wrong?
Cheers,
Attila
The text was updated successfully, but these errors were encountered: