remove references to the OpenCL Extension Specification (#1503)

* remove references to the OpenCL Extension Specification

This is not needed and is incorrect now that OpenCL extensions have
been integrated into the main specification.

Also, fixes numerous issues in the Associated OpenCL Specifications
section.

* tidy up one part of the OpenCL C specification for extensions

We cannot remove OpenCL C references to the OpenCL extension specification
completely because extension pragmas and defines are still described in the
OpenCL extension specification.

Author: bashbaug

OpenCL_C.txt

@@ -96,8 +96,8 @@ what versions of OpenCL C specify that feature.
      is used, it has the identical meaning.
   * Requires support for OpenCL C 2.0, or OpenCL C 3.0 or newer and the
     {opencl_c_feature_name} feature:
-    Features that were introduced in OpenCL C 2.0 as mandatory, but made
-    <<optional-functionality, optional>> in OpenCL C 3.0.
+    Features that were introduced in OpenCL C 2.0 as mandatory, but are
+    <<optional-functionality, optional>> in OpenCL C 3.0 or newer.
     Compilers for versions of OpenCL C 1.2 or below will not provide these
     features, compilers for OpenCL C 2.0 will provide these features,
     compilers for OpenCL C 3.0 or newer may provide these features.
@@ -282,13 +282,13 @@ corresponding optional functionality.
 === Extensions
 
 Other optional functionality may be described by language extensions to OpenCL
-C. Extensions are described in the <<opencl-extension-spec,OpenCL Extension
-Specification>>.  When an OpenCL C extension is supported an associated
-__extension macro__ will be predefined.  Please refer to the OpenCL Extension
-Specification for more information about predefined extension macros.
-
-Prior to OpenCL C 3.0, support for some optional core language features was
-indicated using predefined extension macros.
+C.
+Extensions to OpenCL C are described in the OpenCL C specification or in
+vendor-provided documentation.
+When an OpenCL C extension is supported an associated extension macro will be
+predefined.
+Please refer to the <<opencl-extension-spec,OpenCL Extension Specification>> for
+more information about predefined extension macros.
 
 When an optional core language feature began as an extension it may have both an
 associated feature macro and an associated extension macro.  If an optional core

api/embedded_profile.asciidoc

@@ -6,11 +6,10 @@
 
 The OpenCL specification describes the feature requirements for desktop
 platforms.
-This section describes the OpenCL embedded profile that allows us to
-target a subset of the OpenCL specification for handheld and embedded
+This section describes the OpenCL embedded profile, which defines
+a subset of the OpenCL specification for handheld and embedded
 platforms.
-The optional extensions defined in the OpenCL Extension Specification
-apply to both profiles.
+Optional OpenCL extensions may apply to both profiles.
 
 The OpenCL embedded profile has the following restrictions until version 2.0 (i.e. the optionality described below was <<unified-spec, deprecated by>> version 2.0):
 

api/opencl_assoc_spec.asciidoc

@@ -1,46 +1,35 @@
 // Copyright 2017-2026 The Khronos Group Inc.
 // SPDX-License-Identifier: CC-BY-4.0
 
-= Associated OpenCL specification
+= Associated OpenCL Specifications
+
+
+[[opencl-c-kernel-language]]
+== The OpenCL C Kernel Language
+
+The OpenCL C kernel language is defined in the OpenCL C unified
+specification, which specifies all versions of OpenCL C.
+When an OpenCL device supports one or more versions of the OpenCL C kernel
+language (see {CL_DEVICE_OPENCL_C_VERSION} and
+{CL_DEVICE_OPENCL_C_ALL_VERSIONS}), OpenCL program objects may be created by
+passing OpenCL C source strings to {clCreateProgramWithSource}.
 
 
 [[spirv-il]]
 == SPIR-V Intermediate Language
 
-OpenCL 2.1 and 2.2 require support for the SPIR-V intermediate
-language that allows offline compilation to a binary
-format that may be consumed by the {clCreateProgramWithIL} interface.
-
-The OpenCL specification includes a specification for the SPIR-V
-intermediate language as a cross-platform input language.
-In addition, platform vendors may support their own IL if this is
-appropriate.
-The OpenCL runtime will return a list of supported IL versions using the
-{CL_DEVICE_IL_VERSION} or {CL_DEVICE_ILS_WITH_VERSION} parameter to
-the {clGetDeviceInfo} query.
+The OpenCL specifications include the SPIR-V specification, which defines a
+cross-platform intermediate language.
+When an OpenCL device supports one or more versions of SPIR-V (see
+{CL_DEVICE_IL_VERSION} or {CL_DEVICE_ILS_WITH_VERSION}), OpenCL program objects
+may be created by passing SPIR-V to {clCreateProgramWithIL}.
 
 
 [[opencl-extensions]]
 == Extensions to OpenCL
 
 In addition to the specification of core features, OpenCL provides a number
-of extensions to the API, kernel language or intermediate representation.
-These features are defined in the OpenCL extension specification document.
-
-Extensions defined against earlier versions of the OpenCL specifications,
-whether the API or language specification, are defined in the matching
-versions of the extension specification document.
-
-[[opencl-c-kernel-language]]
-== The OpenCL C Kernel Language
+of extensions to the API, kernel language, or intermediate representation.
+These extensions are described in the OpenCL specifications or in vendor-provided
+documentation.
 
-The OpenCL C kernel language is not defined in the OpenCL unified
-specification.
-The OpenCL C kernel languages are instead defined in the OpenCL 1.0,
-OpenCL 1.1, OpenCL 1.2, OpenCL C 2.0 Kernel Language, and OpenCL C 3.0
-Kernel Language specifications.
-When OpenCL devices support one or more versions of the OpenCL C
-kernel language (see {CL_DEVICE_OPENCL_C_VERSION} and
-{CL_DEVICE_OPENCL_C_ALL_VERSIONS}),
-OpenCL program objects may be created by passing OpenCL C source
-strings to {clCreateProgramWithSource}.

api/opencl_platform_layer.asciidoc

@@ -1490,8 +1490,8 @@ include::{generated}/api/version-notes/CL_DEVICE_EXTENSIONS.asciidoc[]
         {cl_khr_depth_images_EXT} +
         {cl_khr_image2d_from_buffer_EXT}
 
-        Please refer to the OpenCL Extension Specification or vendor
-        provided documentation for a detailed description of these extensions.
+        Please refer to the OpenCL Specification or vendor-provided
+        documentation for a detailed description of these extensions.
 
 | {CL_DEVICE_EXTENSIONS_WITH_VERSION_anchor}
 
@@ -3109,7 +3109,7 @@ include::{generated}/api/version-notes/CL_CONTEXT_INTEROP_USER_SYNC.asciidoc[]
   | {cl_bool_TYPE}
       | Specifies whether the user is responsible for synchronization
         between OpenCL and other APIs.
-        Please refer to the specific sections in the OpenCL Extension
+        Please refer to the specific sections in the OpenCL
         Specification that describe sharing with other APIs for restrictions
         on using this flag.