Join does not always respect the order of provided parameters (oneapi) (#3511)(#3513) #3667
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When 2 arrays have a common base (JIT), the order of the join was not respected. This fix is already applied to opencl, cuda an cpu before although not yet for oneapi.
Description
28bd60b0: adds the the function toTempFormat to the test helpers. This function generates the different temporary array formats (JIT array, SUB-array, Linear array, ...) used by arrayfire.
811669f: The JIT kernel generation is adapted so that the order of the parameters is respected in the write out of the results.
BUG
BEFORE RANDOM RESULTS ARE GENERATED, BECAUSE THE RESULTS were written in the wrong arrays (depending on internal presentation)
ONEAPI, BECAUSE ALREADY FIXED IN THE OTHER BACKENDS
NONE
DIFFICULT
NONE
Fixes: #3511 #3513
Changes to Users
BUG FIX, difficult to detect.
Checklist