| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Do not merge yet. |
Sorry, something went wrong.
|
Code is updated and join tests are expanded with the generation of multiple join combinations. For some joins, the kernel of a previous join could be used since both generated the same 'unique' funcName (while having a different kernel) resulting in the reuse of the previously cached kernel iso generating the new one. |
Sorry, something went wrong.
|
Updated the getFuncName parameters in oneapi. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Arrays were be joined in the order the JIT engine generated the arrays iso the order of the parameters.
Description
This assumption is violated when one of the generated arrays is an intermediate result of a previous specified JIT generated array.
Example of error condition:
af::array A{af::constant(1.,10)}; af::array R{af::join(0,-A,A)}; --> generated af::join(0,A,-A) because A is an intermediate result of -A.In this fix, the order of the parameters is imposed, independent from the order of JIT generation.
PS: This bug appears in OPENCL and CUDA.
As result, a different kernel could be executed than intended, dependent on the order of the JIT kernel generation.
Additional information about the PR answering following questions:
Fixes: #3511
Changes to Users
None
Checklist