From 11df2bd5608c6460c79d9202b9e2d732e5131e6d Mon Sep 17 00:00:00 2001 From: Greg Lueck Date: Mon, 10 Jul 2023 10:39:32 -0400 Subject: [PATCH 1/2] [SYCL][Doc] Update restrictions in extension Update the description of the limitations in the "sycl_ext_oneapi_device_architecture" extension. The newly added host APIs in that extension do not have the same restrictions as the `if_architecture_is` function. --- .../sycl_ext_oneapi_device_architecture.asciidoc | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/sycl/doc/extensions/experimental/sycl_ext_oneapi_device_architecture.asciidoc b/sycl/doc/extensions/experimental/sycl_ext_oneapi_device_architecture.asciidoc index 9c78298c7b876..94e0dba2f5475 100644 --- a/sycl/doc/extensions/experimental/sycl_ext_oneapi_device_architecture.asciidoc +++ b/sycl/doc/extensions/experimental/sycl_ext_oneapi_device_architecture.asciidoc @@ -51,10 +51,10 @@ change incompatibly in future versions of {dpcpp} without prior notice. specification.* There are important limitations with the {dpcpp} implementation of this -experimental extension. In particular, this extension may only be used when -the application is compiled in AOT mode. See the section below titled -"Limitations with the experimental version" for a full description of the -limitations. +experimental extension. In particular, some parts of this extension may only +be used when the application is compiled in AOT mode. See the section below +titled "Limitations with the experimental version" for a full description of +the limitations. == Overview @@ -578,8 +578,9 @@ case syclex::architecture::intel_gpu_bdw: == Limitations with the experimental version The {dpcpp} implementation of this extension currently has some important -limitations. The application must be compiled in ahead-of-time (AOT) mode -using `-fsycl-targets=` where `` is one of the +limitations with the `if_architecture_is` free function. In order to use this +feature, the application must be compiled in ahead-of-time (AOT) mode using +`-fsycl-targets=` where `` is one of the "special target values" listed in the link:../../UsersManual.md[users manual] description of the `-fsycl-targets` option. These are the target names of the form "intel_gpu_*", "nvidia_gpu_*", or "amd_gpu_*". From f97f2997bfe7f2f87b6dbe1a31adc6bc636eb8eb Mon Sep 17 00:00:00 2001 From: Greg Lueck Date: Mon, 10 Jul 2023 13:01:24 -0400 Subject: [PATCH 2/2] List restrictions for Nvidia and AMD devices --- .../sycl_ext_oneapi_device_architecture.asciidoc | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/sycl/doc/extensions/experimental/sycl_ext_oneapi_device_architecture.asciidoc b/sycl/doc/extensions/experimental/sycl_ext_oneapi_device_architecture.asciidoc index 94e0dba2f5475..cfe3349c60554 100644 --- a/sycl/doc/extensions/experimental/sycl_ext_oneapi_device_architecture.asciidoc +++ b/sycl/doc/extensions/experimental/sycl_ext_oneapi_device_architecture.asciidoc @@ -585,6 +585,11 @@ feature, the application must be compiled in ahead-of-time (AOT) mode using description of the `-fsycl-targets` option. These are the target names of the form "intel_gpu_*", "nvidia_gpu_*", or "amd_gpu_*". +The two APIs `device::ext_oneapi_architecture_is` and the +`ext::oneapi::experimental::info::device::architecture` device descriptor are +currently supported only for Intel devices (both GPU and CPU). There is no +support yet for Nvidia or AMD devices. + == Future direction