Skip to content

Conversation

@ph0b
Copy link
Contributor

@ph0b ph0b commented Feb 25, 2025

Previous implementation was returning native and preferred vector widths using an heuristic based on native simd width.

Especially on simd8 GPUs (Intel Arc Alchemist and Flex Series), this approach is incorrect and doesn't match what OpenCL returns.

This set of changes aligns the behavior with OpenCL, defined here: https://github.com/intel/compute-runtime/blob/291745cdf76d83f5dc40e7ef41d347366235ccdb/opencl/source/cl_device/cl_device_caps.cpp#L236

Previous implementation was returning native and preferred vector widths using an heuristic based on native simd width. 

On simd8 GPUs (Intel Arc Alchemist and Flex Series), this approach is incorrect and doesn't match what OpenCL returns.

This set of changes aligns the behavior with OpenCL, defined here: https://github.com/intel/compute-runtime/blob/291745cdf76d83f5dc40e7ef41d347366235ccdb/opencl/source/cl_device/cl_device_caps.cpp#L236
@ph0b ph0b requested a review from a team as a code owner February 25, 2025 13:52
@github-actions github-actions bot added the level-zero L0 adapter specific issues label Feb 25, 2025
@nrspruit
Copy link
Contributor

Hello @ph0b ,

you will want to move this to:
https://github.com/intel/llvm

Unified Runtime -> intel/llvm Repo Move Notice
Information
The source code of Unified Runtime has been moved to intel/llvm under the unified-runtime top-level directory,
all future development will now be carried out there. This was done in intel/llvm#17043.

The code will be mirrored to oneapi-src/unified-runtime and the specification will continue to be hosted at oneapi-src.github.io/unified-runtime.

The contribution guide has been updated with new instructions for contributing to Unified Runtime.

PR Migration
All open PRs including this one will be labelled auto-close and shall be automatically closed after 30 days.
To allow for some breathing space, this automation will not be enabled until next week (27/02/2025).

Should you wish to continue with your PR you will need to migrate it to intel/llvm.
We have provided a script to help automate this process.

@ph0b
Copy link
Contributor Author

ph0b commented Feb 25, 2025

Hello @nrspruit,
thanks for the info - I've migrated this PR to intel/llvm#17178

@ph0b ph0b closed this Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

level-zero L0 adapter specific issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants