Skip to content

[SYCL][Doc] Add initial draft of the targets registry #18822

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

Open
wants to merge 1 commit into
base: sycl
Choose a base branch
from

Conversation

jdnk
Copy link
Contributor

@jdnk jdnk commented Jun 5, 2025

This PR adds a registry containing enumerator values of device targets, features and architectures to be used with the SPV_INTEL_function_variants extension (and other extensions that find it useful). See the README file for details.

The purpose of the PR is to iterate on the registry format before filling in all the entries.

Targets and features come from inspecting compiler output (llc --version and llc --mtriple=<target> -mattr=help). A bulk of the architectures I took directly from sycl_ext_oneapi_device_architecture (mostly the GPUs). Others I added by hand (eg. Intel and ARM CPUs).

Open questions:

  • There could be other ways how to categorize the Intel CPU architectures. I opted strictly for the microarchitecture, another possibility is by the processor name / codename (eg. Meteor Lake instead of Redwood Cove + Crestmont). This may apply for other architectures as well.
  • Should we add only Intel architectures and let other vendors fill their own? For adoption, it would be better to add as many as we can, but we risk landing on architecture ordering different from what the vendor would prefer.
    ** During version 0 we can pre-add values for other vendors and let vendors take over before "freezing" version 1.

@jdnk jdnk requested a review from a team as a code owner June 5, 2025 09:35
@jdnk jdnk changed the title Add initial draft of the targets registry [SYCL][Doc] Add initial draft of the targets registry Jun 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant