[SYCL][DOC] Change extension names to lower case (intel#5607)

I found the all-upper-case names difficult to read, especially in a directory listing where all the files are upper case. Change them all to lower case. The name of the extension and the name of the file are now lower case. The name of the feature-test macro remains upper case.
smaslov-intel · Feb 19, 2022 · d398743 · d398743
1 parent 2711ddd
commit d398743
Show file tree

Hide file tree

Showing 71 changed files with 112 additions and 112 deletions.
diff --git a/sycl/ReleaseNotes.md b/sycl/ReleaseNotes.md
diff --git a/sycl/doc/EnvironmentVariables.md b/sycl/doc/EnvironmentVariables.md
@@ -20,7 +20,7 @@ compiler and runtime.
 | `SYCL_CACHE_THRESHOLD` | Positive integer | Cache eviction threshold in days (default value is 7 for 1 week). Set to 0 for disabling time-based cache eviction. |
 | `SYCL_CACHE_MIN_DEVICE_IMAGE_SIZE` | Positive integer | Minimum size of device code image in bytes which is reasonable to cache on disk because disk access operation may take more time than do JIT compilation for it. Default value is 0 to cache all images. |
 | `SYCL_CACHE_MAX_DEVICE_IMAGE_SIZE` | Positive integer | Maximum size of device image in bytes which is cached. Too big kernels may overload disk too fast. Default value is 1 GB. |
-| `SYCL_ENABLE_DEFAULT_CONTEXTS` | '1' or '0' | Enable ('1') or disable ('0') creation of default platform contexts in SYCL runtime. The default context for each platform contains all devices in the platform. Refer to [Platform Default Contexts](extensions/supported/SYCL_EXT_ONEAPI_DEFAULT_CONTEXT.asciidoc) extension to learn more. Enabled by default on Linux and disabled on Windows. |
+| `SYCL_ENABLE_DEFAULT_CONTEXTS` | '1' or '0' | Enable ('1') or disable ('0') creation of default platform contexts in SYCL runtime. The default context for each platform contains all devices in the platform. Refer to [Platform Default Contexts](extensions/supported/sycl_ext_oneapi_default_context.asciidoc) extension to learn more. Enabled by default on Linux and disabled on Windows. |
 | `SYCL_USM_HOSTPTR_IMPORT` | Integer | Enable by specifying non-zero value. Buffers created with a host pointer will result in host data promotion to USM, improving data transfer performance. To use this feature, also set SYCL_HOST_UNIFIED_MEMORY=1. |
 
 `(*) Note: Any means this environment variable is effective when set to any non-null value.`

diff --git a/sycl/doc/GetStartedGuide.md b/sycl/doc/GetStartedGuide.md
@@ -705,7 +705,7 @@ SYCL_BE=PI_CUDA ./simple-sycl-app-cuda.exe
 
 **NOTE**: DPC++/SYCL developers can specify SYCL device for execution using
 device selectors (e.g. `cl::sycl::cpu_selector`, `cl::sycl::gpu_selector`,
-[Intel FPGA selector(s)](extensions/supported/SYCL_EXT_INTEL_FPGA_DEVICE_SELECTOR.md)) as
+[Intel FPGA selector(s)](extensions/supported/sycl_ext_intel_fpga_device_selector.md)) as
 explained in following section [Code the program for a specific
 GPU](#code-the-program-for-a-specific-gpu).
 

diff --git a/sycl/doc/MultiTileCardWithLevelZero.md b/sycl/doc/MultiTileCardWithLevelZero.md
@@ -24,7 +24,7 @@ One is using environment variable SYCL_DEVICE_FILTER described in [EnvironmentVa
 $ SYCL_DEVICE_FILTER=level_zero sycl-ls
 [level_zero:0] GPU : Intel(R) Level-Zero 1.1 [1.1.19792]
 ```
-Another way is to use similar SYCL API described in [SYCL\_EXT\_ONEAPI\_FILTER\_SELECTOR](extensions/supported/SYCL_EXT_ONEAPI_FILTER_SELECTOR.asciidoc)
+Another way is to use similar SYCL API described in [sycl\_ext\_oneapi\_filter\_selector](extensions/supported/sycl_ext_oneapi_filter_selector.asciidoc)
 E.g. `filter_selector("level_zero")` will only see Level-Zero operated devices.
 
 If there are multiple GPUs in a system then they will be seen as multiple different root-devices.

diff --git a/sycl/doc/design/CompileTimeProperties.md b/sycl/doc/design/CompileTimeProperties.md
@@ -1,12 +1,12 @@
 # Implementation design for compile time constant properties
 
 This document describes the implementation design for the DPC++ extension
-[SYCL\_EXT\_ONEAPI\_PROPERTIES][1], which adds a general mechanism for
+[sycl\_ext\_oneapi\_properties][1], which adds a general mechanism for
 specifying properties which are known at compile time.  This extension is not
 itself a feature, but rather a building block that can be incorporated into
 other features.
 
-[1]: <../extensions/proposed/SYCL_EXT_ONEAPI_PROPERTIES.asciidoc>
+[1]: <../extensions/proposed/sycl_ext_oneapi_properties.asciidoc>
 
 There are a number of situations where we plan to use compile-time constant
 properties, but this design document does not attempt to address them all.
@@ -38,9 +38,9 @@ transformation is done.
 
 One use for compile-time properties is with types that are used exclusively
 for declaring global variables.  One such example is the
-[SYCL\_EXT\_ONEAPI\_DEVICE\_GLOBAL][2] extension:
+[sycl\_ext\_oneapi\_device\_global][2] extension:
 
-[2]: <../extensions/proposed/SYCL_EXT_ONEAPI_DEVICE_GLOBAL.asciidoc>
+[2]: <../extensions/proposed/sycl_ext_oneapi_device_global.asciidoc>
 
 ```
 namespace sycl::ext::oneapi {
@@ -144,11 +144,11 @@ order to do this translation.
 ## Properties on kernel arguments
 
 Another use of compile-time properties is with types that are used to define
-kernel arguments.  For example, the [SYCL\_ONEAPI\_accessor\_properties][6]
+kernel arguments.  For example, the [sycl\_ext\_oneapi\_accessor\_properties][6]
 extension could be redesigned to use compile-time properties.  Such a redesign
 might look like:
 
-[6]: <../extensions/supported/SYCL_EXT_ONEAPI_ACCESSOR_PROPERTIES.asciidoc>
+[6]: <../extensions/supported/sycl_ext_oneapi_accessor_properties.asciidoc>
 
 ```
 namespace sycl {
@@ -270,11 +270,11 @@ the property value to a string if it is not already a string.
 ## Properties on kernel functions
 
 Compile-time properties can also be used to decorate kernel functions as with
-the [SYCL\_EXT\_ONEAPI\_PROPERTIES][8] extension.  There are two ways the
+the [sycl\_ext\_oneapi\_properties][8] extension.  There are two ways the
 application can specify these properties.  The first is by passing a
 `property_list` parameter to the function that submits the kernel:
 
-[8]: <../extensions/proposed/SYCL_EXT_ONEAPI_PROPERTIES.asciidoc>
+[8]: <../extensions/proposed/sycl_ext_oneapi_properties.asciidoc>
 
 ```
 namespace sycl {

diff --git a/sycl/doc/design/DeviceGlobal.md b/sycl/doc/design/DeviceGlobal.md
@@ -1,10 +1,10 @@
 # Implementation design for "device\_global"
 
 This document describes the implementation design for the DPC++ extension
-[SYCL\_EXT\_ONEAPI\_DEVICE\_GLOBAL][1], which allows applications to declare
+[sycl\_ext\_oneapi\_device\_global][1], which allows applications to declare
 global variables in device code.
 
-[1]: <../extensions/proposed/SYCL_EXT_ONEAPI_DEVICE_GLOBAL.asciidoc>
+[1]: <../extensions/proposed/sycl_ext_oneapi_device_global.asciidoc>
 
 
 ## Requirements

diff --git a/sycl/doc/design/DeviceLibExtensions.rst b/sycl/doc/design/DeviceLibExtensions.rst
@@ -48,7 +48,7 @@ Invoking `__devicelib_assert_read` after a kernel doesn't imply the kernel has
 assertion failed.
 
 See also: assert_extension_.
-.. _assert_extension: ../extensions/supported/SYCL_EXT_ONEAPI_ASSERT.asciidoc)
+.. _assert_extension: ../extensions/supported/sycl_ext_oneapi_assert.asciidoc)
 
 cl_intel_devicelib_math
 ==========================

diff --git a/sycl/doc/design/OptionalDeviceFeatures.md b/sycl/doc/design/OptionalDeviceFeatures.md
@@ -266,7 +266,7 @@ non-FPGA users may want to use the `device_global` property
 [`device_image_scope`][5], which requires even non-FPGA users to have precise
 control over the way kernels are bundled into device images.
 
-[5]: <../extensions/proposed/SYCL_EXT_ONEAPI_DEVICE_GLOBAL.asciidoc#properties-for-device-global-variables>
+[5]: <../extensions/proposed/sycl_ext_oneapi_device_global.asciidoc#properties-for-device-global-variables>
 
 The new definition of `-fsycl-device-code-split` is as follows:
 

diff --git a/sycl/doc/design/Reduction_status.md b/sycl/doc/design/Reduction_status.md
@@ -8,7 +8,7 @@
 
 There are 2 specifications of the reduction feature and both are still actual:
 
-* `sycl::ext::oneapi::reduction` is described in [this document](../extensions/deprecated/SYCL_EXT_ONEAPI_ND_RANGE_REDUCTIONS.md). This extension is deprecated, and was created as part of a pathfinding/prototyping work before it was added to SYCL 2020 standard.
+* `sycl::ext::oneapi::reduction` is described in [this document](../extensions/deprecated/sycl_ext_oneapi_nd_range_reductions.md). This extension is deprecated, and was created as part of a pathfinding/prototyping work before it was added to SYCL 2020 standard.
 
 * `sycl::reduction` is described in [SYCL 2020 standard](https://www.khronos.org/registry/SYCL/specs/sycl-2020/html/sycl-2020.html#sec:reduction).
 

diff --git a/sycl/doc/design/fpga_io_pipes_design.rst b/sycl/doc/design/fpga_io_pipes_design.rst
@@ -22,7 +22,7 @@ Requirements
 
 Links
 -----
-.. _Spec: ../extensions/supported/SYCL_EXT_INTEL_DATAFLOW_PIPES.asciidoc
+.. _Spec: ../extensions/supported/sycl_ext_intel_dataflow_pipes.asciidoc
 .. _Interesting comment from Ronan: https://github.com/intel/llvm/pull/635#discussion_r325851766
 
 Summary

diff --git a/...SYCL_EXT_ONEAPI_GROUP_ALGORITHMS.asciidoc → ...sycl_ext_oneapi_group_algorithms.asciidoc b/...SYCL_EXT_ONEAPI_GROUP_ALGORITHMS.asciidoc → ...sycl_ext_oneapi_group_algorithms.asciidoc
diff --git a/...ed/SYCL_EXT_ONEAPI_ND_RANGE_REDUCTIONS.md → ...ed/sycl_ext_oneapi_nd_range_reductions.md b/...ed/SYCL_EXT_ONEAPI_ND_RANGE_REDUCTIONS.md → ...ed/sycl_ext_oneapi_nd_range_reductions.md
diff --git a/...ecated/SYCL_EXT_ONEAPI_SUB_GROUP.asciidoc → ...ecated/sycl_ext_oneapi_sub_group.asciidoc b/...ecated/SYCL_EXT_ONEAPI_SUB_GROUP.asciidoc → ...ecated/sycl_ext_oneapi_sub_group.asciidoc
diff --git a/...l/SYCL_EXT_INTEL_BF16_CONVERSION.asciidoc → ...l/sycl_ext_intel_bf16_conversion.asciidoc b/...l/SYCL_EXT_INTEL_BF16_CONVERSION.asciidoc → ...l/sycl_ext_intel_bf16_conversion.asciidoc
diff --git a/...l/SYCL_EXT_INTEL_ESIMD/ESIMD-TODO-list.md → ...l/sycl_ext_intel_esimd/ESIMD-TODO-list.md b/...l/SYCL_EXT_INTEL_ESIMD/ESIMD-TODO-list.md → ...l/sycl_ext_intel_esimd/ESIMD-TODO-list.md
diff --git a/...perimental/SYCL_EXT_INTEL_ESIMD/README.md → ...perimental/sycl_ext_intel_esimd/README.md b/...perimental/SYCL_EXT_INTEL_ESIMD/README.md → ...perimental/sycl_ext_intel_esimd/README.md
@@ -4,7 +4,7 @@ OneAPI provides the "Explicit SIMD" SYCL extension (or simply "ESIMD") for
 lower-level Intel GPU programming. It provides APIs closely matching Intel GPU ISA
 yet allows to write explicitly vectorized device code. This helps programmer to
 have more control over the generated code and depend less on compiler
-optimizations. The [specification](SYCL_EXT_INTEL_ESIMD.md),
+optimizations. The [specification](sycl_ext_intel_esimd.md),
 [API reference](https://intel.github.io/llvm-docs/doxygen/group__sycl__esimd.html), and
 [working code examples](https://github.com/intel/llvm-test-suite/tree/intel/SYCL/ESIMD) are available on the Intel DPC++ project's github.
 

diff --git a/...NTEL_ESIMD/images/Matrix_2_2_2_4__1_2.svg → ...ntel_esimd/images/Matrix_2_2_2_4__1_2.svg b/...NTEL_ESIMD/images/Matrix_2_2_2_4__1_2.svg → ...ntel_esimd/images/Matrix_2_2_2_4__1_2.svg
diff --git a/...NTEL_ESIMD/images/Matrix_4_1_4_2__0_0.svg → ...ntel_esimd/images/Matrix_4_1_4_2__0_0.svg b/...NTEL_ESIMD/images/Matrix_4_1_4_2__0_0.svg → ...ntel_esimd/images/Matrix_4_1_4_2__0_0.svg
diff --git a/...YCL_EXT_INTEL_ESIMD/images/VectorEven.svg → ...ycl_ext_intel_esimd/images/VectorEven.svg b/...YCL_EXT_INTEL_ESIMD/images/VectorEven.svg → ...ycl_ext_intel_esimd/images/VectorEven.svg
diff --git a/...SYCL_EXT_INTEL_ESIMD/images/VectorOdd.svg → ...sycl_ext_intel_esimd/images/VectorOdd.svg b/...SYCL_EXT_INTEL_ESIMD/images/VectorOdd.svg → ...sycl_ext_intel_esimd/images/VectorOdd.svg
diff --git a/...SYCL_EXT_INTEL_ESIMD/images/simd_view.svg → ...sycl_ext_intel_esimd/images/simd_view.svg b/...SYCL_EXT_INTEL_ESIMD/images/simd_view.svg → ...sycl_ext_intel_esimd/images/simd_view.svg
diff --git a/...L_EXT_INTEL_ESIMD/SYCL_EXT_INTEL_ESIMD.md → ...l_ext_intel_esimd/sycl_ext_intel_esimd.md b/...L_EXT_INTEL_ESIMD/SYCL_EXT_INTEL_ESIMD.md → ...l_ext_intel_esimd/sycl_ext_intel_esimd.md
diff --git a/...l/SYCL_EXT_INTEL_ONLINE_COMPILER.asciidoc → ...l/sycl_ext_intel_online_compiler.asciidoc b/...l/SYCL_EXT_INTEL_ONLINE_COMPILER.asciidoc → ...l/sycl_ext_intel_online_compiler.asciidoc
diff --git a/...EXT_ONEAPI_FREE_FUNCTION_QUERIES.asciidoc → ...ext_oneapi_free_function_queries.asciidoc b/...EXT_ONEAPI_FREE_FUNCTION_QUERIES.asciidoc → ...ext_oneapi_free_function_queries.asciidoc
diff --git a/...SYCL_EXT_ONEAPI_GROUP_LOAD_STORE.asciidoc → ...sycl_ext_oneapi_group_load_store.asciidoc b/...SYCL_EXT_ONEAPI_GROUP_LOAD_STORE.asciidoc → ...sycl_ext_oneapi_group_load_store.asciidoc
@@ -1,4 +1,4 @@
-= SYCL_EXT_ONEAPI_GROUP_LOAD_STORE
+= sycl_ext_oneapi_group_load_store
 :source-highlighter: coderay
 :coderay-linenums-mode: table
 

diff --git a/...ental/SYCL_EXT_ONEAPI_GROUP_SORT.asciidoc → ...ental/sycl_ext_oneapi_group_sort.asciidoc b/...ental/SYCL_EXT_ONEAPI_GROUP_SORT.asciidoc → ...ental/sycl_ext_oneapi_group_sort.asciidoc
@@ -1,4 +1,4 @@
-= SYCL_EXT_ONEAPI_GROUP_SORT
+= sycl_ext_oneapi_group_sort
 :source-highlighter: coderay
 :coderay-linenums-mode: table
 

diff --git a/...erimental/SYCL_EXT_ONEAPI_MATRIX.asciidoc → ...erimental/sycl_ext_oneapi_matrix.asciidoc b/...erimental/SYCL_EXT_ONEAPI_MATRIX.asciidoc → ...erimental/sycl_ext_oneapi_matrix.asciidoc
@@ -1,4 +1,4 @@
-# Matrix Programming Extension for DPC++: SYCL_EXT_ONEAPI_MATRIX
+# Matrix Programming Extension for DPC++: sycl_ext_oneapi_matrix
 :source-highlighter: coderay
 :coderay-linenums-mode: table
 :dpcpp: pass:[DPC++]
@@ -567,7 +567,7 @@ for (int i = 0; i < msize; i++)
 
 
 ### Memory scope
-The current experimental API uses `joint_` semantics to define the memory scope of the matrix. The long term solution is to use the proposed link:../supported/SYCL_EXT_ONEAPI_LOCAL_MEMORY.asciidoc[`group_local_memory` extension] to allocate the matrix in local memory associated with a SYCL group as shown in the example below.
+The current experimental API uses `joint_` semantics to define the memory scope of the matrix. The long term solution is to use the proposed link:../supported/sycl_ext_oneapi_local_memory.asciidoc[`group_local_memory` extension] to allocate the matrix in local memory associated with a SYCL group as shown in the example below.
 
 
 ```c++

diff --git a/...l/SYCL_EXT_ONEAPI_MAX_WORK_GROUP_QUERY.md → ...l/sycl_ext_oneapi_max_work_group_query.md b/...l/SYCL_EXT_ONEAPI_MAX_WORK_GROUP_QUERY.md → ...l/sycl_ext_oneapi_max_work_group_query.md
@@ -1,4 +1,4 @@
-# SYCL_EXT_ONEAPI_MAX_WORK_GROUP_QUERY
+# sycl_ext_oneapi_max_work_group_query
 
 ## Notice
 

diff --git a/...imental/SYCL_EXT_ONEAPI_SPEC_CONSTANTS.md → ...imental/sycl_ext_oneapi_spec_constants.md b/...imental/SYCL_EXT_ONEAPI_SPEC_CONSTANTS.md → ...imental/sycl_ext_oneapi_spec_constants.md
diff --git a/...ed/SYCL_EXT_INTEL_DATAFLOW_PIPES.asciidoc → ...ed/sycl_ext_intel_dataflow_pipes.asciidoc b/...ed/SYCL_EXT_INTEL_DATAFLOW_PIPES.asciidoc → ...ed/sycl_ext_intel_dataflow_pipes.asciidoc
@@ -20,7 +20,7 @@
 IMPORTANT: This is a proposed update to an existing extension.  The APIs
 described in this document are not yet implemented and cannot be used in
 application code.  See
-link:../supported/SYCL_EXT_INTEL_DATAFLOW_PIPES.asciidoc[here] for the existing
+link:../supported/sycl_ext_intel_dataflow_pipes.asciidoc[here] for the existing
 extension, which is implemented.
 
 NOTE: Khronos(R) is a registered trademark and SYCL(TM) and SPIR(TM) are trademarks of The Khronos Group Inc.  OpenCL(TM) is a trademark of Apple Inc. used by permission by Khronos.

diff --git a/...sions/proposed/SYCL_EXT_INTEL_FPGA_LSU.md → ...sions/proposed/sycl_ext_intel_fpga_lsu.md b/...sions/proposed/SYCL_EXT_INTEL_FPGA_LSU.md → ...sions/proposed/sycl_ext_intel_fpga_lsu.md
@@ -6,7 +6,7 @@ described in this document are not yet implemented and cannot be used in
 application code.  See [here][1] for the existing extension, which is
 implemented.
 
-[1]: <../supported/SYCL_EXT_INTEL_FPGA_LSU.md>
+[1]: <../supported/sycl_ext_intel_fpga_lsu.md>
 
 The Intel FPGA `lsu` class is implemented in `sycl/ext/intel/fpga_lsu.hpp` which
 is included in `sycl/ext/intel/fpga_extensions.hpp`.

diff --git a/...CL_EXT_ONEAPI_COMPLEX_ALGORITHMS.asciidoc → ...cl_ext_oneapi_complex_algorithms.asciidoc b/...CL_EXT_ONEAPI_COMPLEX_ALGORITHMS.asciidoc → ...cl_ext_oneapi_complex_algorithms.asciidoc
@@ -1,4 +1,4 @@
-= SYCL_EXT_ONEAPI_COMPLEX_ALGORITHMS
+= sycl_ext_oneapi_complex_algorithms
 :source-highlighter: coderay
 :coderay-linenums-mode: table
 

diff --git a/...ed/SYCL_EXT_ONEAPI_DEVICE_GLOBAL.asciidoc → ...ed/sycl_ext_oneapi_device_global.asciidoc b/...ed/SYCL_EXT_ONEAPI_DEVICE_GLOBAL.asciidoc → ...ed/sycl_ext_oneapi_device_global.asciidoc
@@ -1,4 +1,4 @@
-= SYCL_EXT_ONEAPI_DEVICE_GLOBAL
+= sycl_ext_oneapi_device_global
 
 :source-highlighter: coderay
 :coderay-linenums-mode: table

diff --git a/...oposed/SYCL_EXT_ONEAPI_DEVICE_IF.asciidoc → ...oposed/sycl_ext_oneapi_device_if.asciidoc b/...oposed/SYCL_EXT_ONEAPI_DEVICE_IF.asciidoc → ...oposed/sycl_ext_oneapi_device_if.asciidoc
@@ -1,4 +1,4 @@
-= SYCL_EXT_ONEAPI_DEVICE_IF
+= sycl_ext_oneapi_device_if
 :source-highlighter: coderay
 :coderay-linenums-mode: table
 

diff --git a/...EXT_ONEAPI_FREE_FUNCTION_QUERIES.asciidoc → ...ext_oneapi_free_function_queries.asciidoc b/...EXT_ONEAPI_FREE_FUNCTION_QUERIES.asciidoc → ...ext_oneapi_free_function_queries.asciidoc
@@ -1,4 +1,4 @@
-= SYCL_EXT_ONEAPI_FREE_FUNCTION_QUERIES
+= sycl_ext_oneapi_free_function_queries
 :source-highlighter: coderay
 :coderay-linenums-mode: table
 

diff --git a/...osed/SYCL_EXT_ONEAPI_INVOKE_SIMD.asciidoc → ...osed/sycl_ext_oneapi_invoke_simd.asciidoc b/...osed/SYCL_EXT_ONEAPI_INVOKE_SIMD.asciidoc → ...osed/sycl_ext_oneapi_invoke_simd.asciidoc
@@ -1,4 +1,4 @@
-= SYCL_EXT_ONEAPI_INVOKE_SIMD
+= sycl_ext_oneapi_invoke_simd
 :source-highlighter: coderay
 :coderay-linenums-mode: table
 
@@ -53,7 +53,7 @@ Jason Sewall, Intel (jason 'dot' sewall 'at' intel 'dot' com) +
 This extension is written against the SYCL 2020 specification, Revision 4 and the following extensions:
 
 - SPV_INTEL_function_pointers
-- SYCL_EXT_ONEAPI_UNIFORM
+- sycl_ext_oneapi_uniform
 
 == Feature Test Macro
 
@@ -183,7 +183,7 @@ is an error, and an implementation must issue a diagnostic.
 
 To enable overloading in cases where the `Callable` accepts either a scalar
 type or a SIMD type, we leverage the `sycl::ext::oneapi::experimental::uniform` wrapper
-type from the `SYCL_EXT_ONEAPI_UNIFORM` extension.
+type from the `sycl_ext_oneapi_uniform` extension.
 
 Each argument in the `args` parameter pack must be an arithmetic type, a
 trivially copyable type wrapped in a `sycl::ext::oneapi::experimental::uniform`, or a

diff --git a/...YCL_EXT_ONEAPI_KERNEL_PROPERTIES.asciidoc → ...ycl_ext_oneapi_kernel_properties.asciidoc b/...YCL_EXT_ONEAPI_KERNEL_PROPERTIES.asciidoc → ...ycl_ext_oneapi_kernel_properties.asciidoc
@@ -1,4 +1,4 @@
-= SYCL_EXT_ONEAPI_KERNEL_PROPERTIES
+= sycl_ext_oneapi_kernel_properties
 :source-highlighter: coderay
 :coderay-linenums-mode: table
 
@@ -58,7 +58,7 @@ Roland Schulz, Intel
 This extension is written against the SYCL 2020 specification, Revision 4 and
 the following extensions:
 
-- link:SYCL_EXT_ONEAPI_PROPERTIES.asciidoc[SYCL_EXT_ONEAPI_PROPERTIES]
+- link:sycl_ext_oneapi_properties.asciidoc[sycl_ext_oneapi_properties]
 
 == Feature Test Macro
 

diff --git a/...EXT_ONEAPI_LOCAL_STATIC_MEM_USED.asciidoc → ...ext_oneapi_local_static_mem_used.asciidoc b/...EXT_ONEAPI_LOCAL_STATIC_MEM_USED.asciidoc → ...ext_oneapi_local_static_mem_used.asciidoc
diff --git a/...posed/SYCL_EXT_ONEAPI_PROPERTIES.asciidoc → ...posed/sycl_ext_oneapi_properties.asciidoc b/...posed/SYCL_EXT_ONEAPI_PROPERTIES.asciidoc → ...posed/sycl_ext_oneapi_properties.asciidoc
@@ -1,6 +1,6 @@
 :sectnums:
 
-= `SYCL_EXT_ONEAPI_PROPERTIES`
+= `sycl_ext_oneapi_properties`
 
 == Introduction
 

diff --git a/...proposed/SYCL_EXT_ONEAPI_UNIFORM.asciidoc → ...proposed/sycl_ext_oneapi_uniform.asciidoc b/...proposed/SYCL_EXT_ONEAPI_UNIFORM.asciidoc → ...proposed/sycl_ext_oneapi_uniform.asciidoc
@@ -1,4 +1,4 @@
-= SYCL_EXT_ONEAPI_UNIFORM
+= sycl_ext_oneapi_uniform
 :source-highlighter: coderay
 :coderay-linenums-mode: table
 

diff --git a/...d/SYCL_EXT_INTEL_BUFFER_LOCATION.asciidoc → ...d/sycl_ext_intel_buffer_location.asciidoc b/...d/SYCL_EXT_INTEL_BUFFER_LOCATION.asciidoc → ...d/sycl_ext_intel_buffer_location.asciidoc
diff --git a/...ed/SYCL_EXT_INTEL_DATAFLOW_PIPES.asciidoc → ...ed/sycl_ext_intel_dataflow_pipes.asciidoc b/...ed/SYCL_EXT_INTEL_DATAFLOW_PIPES.asciidoc → ...ed/sycl_ext_intel_dataflow_pipes.asciidoc
diff --git a/...s/supported/SYCL_EXT_INTEL_DEVICE_INFO.md → ...s/supported/sycl_ext_intel_device_info.md b/...s/supported/SYCL_EXT_INTEL_DEVICE_INFO.md → ...s/supported/sycl_ext_intel_device_info.md
diff --git a/...ed/SYCL_EXT_INTEL_FPGA_DEVICE_SELECTOR.md → ...ed/sycl_ext_intel_fpga_device_selector.md b/...ed/SYCL_EXT_INTEL_FPGA_DEVICE_SELECTOR.md → ...ed/sycl_ext_intel_fpga_device_selector.md
diff --git a/...ions/supported/SYCL_EXT_INTEL_FPGA_LSU.md → ...ions/supported/sycl_ext_intel_fpga_lsu.md b/...ions/supported/SYCL_EXT_INTEL_FPGA_LSU.md → ...ions/supported/sycl_ext_intel_fpga_lsu.md
diff --git a/...ions/supported/SYCL_EXT_INTEL_FPGA_REG.md → ...ions/supported/sycl_ext_intel_fpga_reg.md b/...ions/supported/SYCL_EXT_INTEL_FPGA_REG.md → ...ions/supported/sycl_ext_intel_fpga_reg.md
diff --git a/...L_EXT_INTEL_KERNEL_ARGS_RESTRICT.asciidoc → ...l_ext_intel_kernel_args_restrict.asciidoc b/...L_EXT_INTEL_KERNEL_ARGS_RESTRICT.asciidoc → ...l_ext_intel_kernel_args_restrict.asciidoc
diff --git a/...L_EXT_INTEL_MEM_CHANNEL_PROPERTY.asciidoc → ...l_ext_intel_mem_channel_property.asciidoc b/...L_EXT_INTEL_MEM_CHANNEL_PROPERTY.asciidoc → ...l_ext_intel_mem_channel_property.asciidoc
@@ -1,4 +1,4 @@
-= SYCL_EXT_INTEL_MEM_CHANNEL_PROPERTY
+= sycl_ext_intel_mem_channel_property
 
 == Introduction
 NOTE: Khronos(R) is a registered trademark and SYCL(TM) and SPIR(TM) are trademarks of The Khronos Group Inc.  OpenCL(TM) is a trademark of Apple Inc. used by permission by Khronos.

diff --git a/...YCL_EXT_INTEL_USM_ADDRESS_SPACES.asciidoc → ...ycl_ext_intel_usm_address_spaces.asciidoc b/...YCL_EXT_INTEL_USM_ADDRESS_SPACES.asciidoc → ...ycl_ext_intel_usm_address_spaces.asciidoc
@@ -1,4 +1,4 @@
-= SYCL_EXT_INTEL_USM_ADDRESS_SPACES
+= sycl_ext_intel_usm_address_spaces
 
 == Introduction
 This extension introduces two new address spaces and their corresponding multi_ptr specializations.  

diff --git a/...L_EXT_ONEAPI_ACCESSOR_PROPERTIES.asciidoc → ...l_ext_oneapi_accessor_properties.asciidoc b/...L_EXT_ONEAPI_ACCESSOR_PROPERTIES.asciidoc → ...l_ext_oneapi_accessor_properties.asciidoc
diff --git a/...supported/SYCL_EXT_ONEAPI_ASSERT.asciidoc → ...supported/sycl_ext_oneapi_assert.asciidoc b/...supported/SYCL_EXT_ONEAPI_ASSERT.asciidoc → ...supported/sycl_ext_oneapi_assert.asciidoc
@@ -1,4 +1,4 @@
-= SYCL_EXT_ONEAPI_ASSERT
+= sycl_ext_oneapi_assert
 
 :source-highlighter: coderay
 :coderay-linenums-mode: table

diff --git a/...ted/SYCL_EXT_ONEAPI_BACKEND_LEVEL_ZERO.md → ...ted/sycl_ext_oneapi_backend_level_zero.md b/...ted/SYCL_EXT_ONEAPI_BACKEND_LEVEL_ZERO.md → ...ted/sycl_ext_oneapi_backend_level_zero.md
@@ -45,7 +45,7 @@ For further details see here: <https://github.com/intel/llvm/blob/sycl/sycl/doc/
 ### 3.2 Through a programming API
         
 There is an extension that introduces a filtering device selection to SYCL described in
-[SYCL\_EXT\_ONEAPI\_FILTER\_SELECTOR](../supported/SYCL_EXT_ONEAPI_FILTER_SELECTOR.asciidoc).
+[sycl\_ext\_oneapi\_filter\_selector](../supported/sycl_ext_oneapi_filter_selector.asciidoc).
 
 Similar to how SYCL_DEVICE_FILTER applies filtering to the entire process this device selector can be used to
 programmatically select the Level-Zero backend.

diff --git a/.../SYCL_EXT_ONEAPI_DEFAULT_CONTEXT.asciidoc → .../sycl_ext_oneapi_default_context.asciidoc b/.../SYCL_EXT_ONEAPI_DEFAULT_CONTEXT.asciidoc → .../sycl_ext_oneapi_default_context.asciidoc
diff --git a/..._EXT_ONEAPI_DISCARD_QUEUE_EVENTS.asciidoc → ..._ext_oneapi_discard_queue_events.asciidoc b/..._EXT_ONEAPI_DISCARD_QUEUE_EVENTS.asciidoc → ..._ext_oneapi_discard_queue_events.asciidoc
@@ -1,4 +1,4 @@
-= SYCL_EXT_ONEAPI_DISCARD_QUEUE_EVENTS
+= sycl_ext_oneapi_discard_queue_events
 :source-highlighter: coderay
 :coderay-linenums-mode: table
 
@@ -168,7 +168,7 @@ enum class event_command_status : int {
 This non-normative section describes the conditions when the DPC++ implementation provides an optimization benefit* for the `discard_events` property.
 
  - The queue must be constructed with the `in_order` property.
- - A kernel submitted to the queue must not use the link:../supported/SYCL_EXT_ONEAPI_ASSERT.asciidoc[fallback assert feature].
+ - A kernel submitted to the queue must not use the link:../supported/sycl_ext_oneapi_assert.asciidoc[fallback assert feature].
  - A queue operation submitted to the queue must not use streams or buffer / image accessors. However, local accessors do not inhibit optimization.
  - Any queue operations using Level Zero backend temporarily work without optimization.
 

diff --git a/...d/SYCL_EXT_ONEAPI_DOT_ACCUMULATE.asciidoc → ...d/sycl_ext_oneapi_dot_accumulate.asciidoc b/...d/SYCL_EXT_ONEAPI_DOT_ACCUMULATE.asciidoc → ...d/sycl_ext_oneapi_dot_accumulate.asciidoc
diff --git a/.../SYCL_EXT_ONEAPI_ENQUEUE_BARRIER.asciidoc → .../sycl_ext_oneapi_enqueue_barrier.asciidoc b/.../SYCL_EXT_ONEAPI_ENQUEUE_BARRIER.asciidoc → .../sycl_ext_oneapi_enqueue_barrier.asciidoc
@@ -1,4 +1,4 @@
-= SYCL_EXT_ONEAPI_ENQUEUE_BARRIER
+= sycl_ext_oneapi_enqueue_barrier
 :source-highlighter: coderay
 :coderay-linenums-mode: table
 

diff --git a/...SYCL_EXT_ONEAPI_EXTENDED_ATOMICS.asciidoc → ...sycl_ext_oneapi_extended_atomics.asciidoc b/...SYCL_EXT_ONEAPI_EXTENDED_ATOMICS.asciidoc → ...sycl_ext_oneapi_extended_atomics.asciidoc
diff --git a/.../SYCL_EXT_ONEAPI_FILTER_SELECTOR.asciidoc → .../sycl_ext_oneapi_filter_selector.asciidoc b/.../SYCL_EXT_ONEAPI_FILTER_SELECTOR.asciidoc → .../sycl_ext_oneapi_filter_selector.asciidoc
diff --git a/...SYCL_EXT_ONEAPI_GROUP_ALGORITHMS.asciidoc → ...sycl_ext_oneapi_group_algorithms.asciidoc b/...SYCL_EXT_ONEAPI_GROUP_ALGORITHMS.asciidoc → ...sycl_ext_oneapi_group_algorithms.asciidoc
@@ -1,2 +1,2 @@
 This extension has been deprecated, but the specification is still available
-link:../deprecated/SYCL_EXT_ONEAPI_GROUP_ALGORITHMS.asciidoc[here].
+link:../deprecated/sycl_ext_oneapi_group_algorithms.asciidoc[here].
diff --git a/...ted/SYCL_EXT_ONEAPI_LOCAL_MEMORY.asciidoc → ...ted/sycl_ext_oneapi_local_memory.asciidoc b/...ted/SYCL_EXT_ONEAPI_LOCAL_MEMORY.asciidoc → ...ted/sycl_ext_oneapi_local_memory.asciidoc
@@ -1,4 +1,4 @@
-= SYCL_EXT_ONEAPI_LOCAL_MEMORY
+= sycl_ext_oneapi_local_memory
 
 :source-highlighter: coderay
 :coderay-linenums-mode: table

diff --git a/...ed/SYCL_EXT_ONEAPI_ND_RANGE_REDUCTIONS.md → ...ed/sycl_ext_oneapi_nd_range_reductions.md b/...ed/SYCL_EXT_ONEAPI_ND_RANGE_REDUCTIONS.md → ...ed/sycl_ext_oneapi_nd_range_reductions.md
@@ -1,4 +1,4 @@
 This extension has been deprecated, but the specification is still available
 [here][1].
 
-[1]: <../deprecated/SYCL_EXT_ONEAPI_ND_RANGE_REDUCTIONS.md>
+[1]: <../deprecated/sycl_ext_oneapi_nd_range_reductions.md>
diff --git a/...s/supported/SYCL_EXT_ONEAPI_SRGB.asciidoc → ...s/supported/sycl_ext_oneapi_srgb.asciidoc b/...s/supported/SYCL_EXT_ONEAPI_SRGB.asciidoc → ...s/supported/sycl_ext_oneapi_srgb.asciidoc
@@ -1,4 +1,4 @@
-= SYCL_EXT_ONEAPI_SRGB
+= sycl_ext_oneapi_srgb
 :source-highlighter: coderay
 :coderay-linenums-mode: table
 

diff --git a/...ported/SYCL_EXT_ONEAPI_SUB_GROUP.asciidoc → ...ported/sycl_ext_oneapi_sub_group.asciidoc b/...ported/SYCL_EXT_ONEAPI_SUB_GROUP.asciidoc → ...ported/sycl_ext_oneapi_sub_group.asciidoc
@@ -1,2 +1,2 @@
 This extension has been deprecated, but the specification is still available
-link:../deprecated/SYCL_EXT_ONEAPI_SUB_GROUP.asciidoc[here].
+link:../deprecated/sycl_ext_oneapi_sub_group.asciidoc[here].
diff --git a/...d/SYCL_EXT_ONEAPI_SUB_GROUP_MASK.asciidoc → ...d/sycl_ext_oneapi_sub_group_mask.asciidoc b/...d/SYCL_EXT_ONEAPI_SUB_GROUP_MASK.asciidoc → ...d/sycl_ext_oneapi_sub_group_mask.asciidoc
@@ -1,4 +1,4 @@
-= SYCL_EXT_ONEAPI_SUB_GROUP_MASK
+= sycl_ext_oneapi_sub_group_mask
 :source-highlighter: coderay
 :coderay-linenums-mode: table
 

diff --git a/..._USE_PINNED_HOST_MEMORY_PROPERTY.asciidoc → ..._use_pinned_host_memory_property.asciidoc b/..._USE_PINNED_HOST_MEMORY_PROPERTY.asciidoc → ..._use_pinned_host_memory_property.asciidoc
diff --git a/sycl/include/CL/sycl/detail/type_traits.hpp b/sycl/include/CL/sycl/detail/type_traits.hpp
@@ -58,7 +58,7 @@ __SYCL_INLINE_CONSTEXPR bool is_group_v =
 namespace detail {
 // Type for Intel device UUID extension.
 // For details about this extension, see
-// sycl/doc/extensions/supported/SYCL_EXT_INTEL_DEVICE_INFO.md
+// sycl/doc/extensions/supported/sycl_ext_intel_device_info.md
 using uuid_type = std::array<unsigned char, 16>;
 
 template <typename T, typename R> struct copy_cv_qualifiers;

diff --git a/sycl/include/sycl/ext/intel/experimental/esimd.hpp b/sycl/include/sycl/ext/intel/experimental/esimd.hpp
@@ -15,7 +15,7 @@
 /// @defgroup sycl_esimd DPC++ Explicit SIMD API
 /// This is a low-level API providing direct access to Intel GPU hardware
 /// features. ESIMD overview can be found
-/// [here](https://github.com/intel/llvm/blob/sycl/sycl/doc/extensions/experimental/SYCL_EXT_INTEL_ESIMD/SYCL_EXT_INTEL_ESIMD.md).
+/// [here](https://github.com/intel/llvm/blob/sycl/sycl/doc/extensions/experimental/sycl_ext_intel_esimd/sycl_ext_intel_esimd.md).
 /// Some terminology used in the API documentation:
 /// - *lane* -
 ///       (or "vector lane") Individual "lane" of input and output elements

diff --git a/sycl/include/sycl/ext/oneapi/group_local_memory.hpp b/sycl/include/sycl/ext/oneapi/group_local_memory.hpp
@@ -35,7 +35,7 @@ std::enable_if_t<std::is_trivially_destructible<T>::value &&
   return reinterpret_cast<__attribute__((opencl_local)) T *>(AllocatedMem);
 #else
   throw feature_not_supported(
-      "SYCL_EXT_ONEAPI_LOCAL_MEMORY extension is not supported on host device",
+      "sycl_ext_oneapi_local_memory extension is not supported on host device",
       PI_INVALID_OPERATION);
 #endif
 }
@@ -60,7 +60,7 @@ std::enable_if_t<std::is_trivially_destructible<T>::value &&
   // Silence unused variable warning
   [&args...] {}();
   throw feature_not_supported(
-      "SYCL_EXT_ONEAPI_LOCAL_MEMORY extension is not supported on host device",
+      "sycl_ext_oneapi_local_memory extension is not supported on host device",
       PI_INVALID_OPERATION);
 #endif
 }

diff --git a/sycl/plugins/cuda/pi_cuda.cpp b/sycl/plugins/cuda/pi_cuda.cpp
@@ -1744,7 +1744,7 @@ pi_result cuda_piDeviceGetInfo(pi_device device, pi_device_info param_name,
   case PI_DEVICE_INFO_MAX_MEM_BANDWIDTH:
     // TODO: Check if Intel device UUID extension is utilized for CUDA.
     // For details about this extension, see
-    // sycl/doc/extensions/supported/SYCL_EXT_INTEL_DEVICE_INFO.md
+    // sycl/doc/extensions/supported/sycl_ext_intel_device_info.md
   case PI_DEVICE_INFO_UUID:
     return PI_INVALID_VALUE;