[UR] Update SetErrorMessage implementations to have correct type for ErrorCode param #18260
Assignees
Labels
Comments
martygrant
changed the title
martygrant
changed the title
martygrant
added a commit
that referenced
this issue
May 7, 2025
…_t for the urAdapterGetLastError entry point (#18264) Fixes #18260 Also updates `checkUrResult` in SYCL RT to remove warning level check as `urAdapterGetLastError` is now only used for errors. --------- Co-authored-by: Kenneth Benzie (Benie) <[email protected]>
github-actions bot
pushed a commit
to oneapi-src/unified-runtime
that referenced
this issue
May 8, 2025
…urAdapterGetLastError entry point (#18264) Fixes intel/llvm#18260 Also updates `checkUrResult` in SYCL RT to remove warning level check as `urAdapterGetLastError` is now only used for errors. --------- Co-authored-by: Kenneth Benzie (Benie) <[email protected]>
kbenzie
added a commit
to oneapi-src/unified-runtime
that referenced
this issue
May 8, 2025
…urAdapterGetLastError entry point (#18264) Fixes intel/llvm#18260 Also updates `checkUrResult` in SYCL RT to remove warning level check as `urAdapterGetLastError` is now only used for errors. --------- Co-authored-by: Kenneth Benzie (Benie) <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As discussed in #18182 (comment) the common function
SetErrorMessagewhich is used to set the message retrieved when using theurAdapterGetLastErrorentry point is expecting aur_result_tfor theErrorCodeparam but should instead beint32_t, this occurs in most adapter implementations.The text was updated successfully, but these errors were encountered: