Closed sarnex closed 1 month ago
It's likely this is caused by the Aug 27th pulldown.
Looks like jchlanda is working on a similar crash with the same backtrace. Please unassign if it's not the same thing
This has been already fixed upstream, please see: https://github.com/llvm/llvm-project/pull/103713
I suggest cherry-picking the upstream patch, or perhaps commenting out the assert (as the fix is basically doing an early exit on the same condition as the assert) and waiting for the pull down. Commenting out the assert will be safe as the implementation of the function in question is aware of a possible type mis-match and handles it well (https://github.com/intel/llvm/blob/sycl/llvm/lib/Analysis/ValueTracking.cpp#L3600).
Added a cherry pick https://github.com/intel/llvm/pull/15347
Describe the bug
Seems it's actually a compiler assert:
To reproduce
No response
Environment
No response
Additional context
No response