Skip to content
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

[SYCL] Don't set PI_USM_INDIRECT_ACCESS if platform don't support it #12780

Merged

Commits on Feb 20, 2024

  1. [SYCL] Don't set PI_USM_INDIRECT_ACCESS if platform don't support it

    If the OpenCL platform doesn't support USM, don't set
    PI_USM_INDIRECT_ACCESS exec info. This will avoid SYCL program to fail
    when they don't use USM. If the program do need USM support, the runtime will fail
    on other API calls (like memory allocation).
    
    Signed-off-by: Victor Lomuller <victor@codeplay.com>
    Naghasan committed Feb 20, 2024
    Configuration menu
    Copy the full SHA
    f12b881 View commit details
    Browse the repository at this point in the history

Commits on Feb 21, 2024

  1. Configuration menu
    Copy the full SHA
    f26b248 View commit details
    Browse the repository at this point in the history
  2. fix e2e test

    Naghasan committed Feb 21, 2024
    Configuration menu
    Copy the full SHA
    1a7ebb0 View commit details
    Browse the repository at this point in the history

Commits on Feb 22, 2024

  1. Configuration menu
    Copy the full SHA
    315e0d1 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    db1fc13 View commit details
    Browse the repository at this point in the history

Commits on Feb 27, 2024

  1. Configuration menu
    Copy the full SHA
    628cc45 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    8d7ff8d View commit details
    Browse the repository at this point in the history