Use domain-specific macros instead

uxlfoundation · Sep 17, 2024 · facd75a · facd75a
1 parent 992ddbf
commit facd75a
Showing 1 changed file with 13 additions and 6 deletions.
diff --git a/source/elements/oneMKL/source/architecture/other_architecture.inc.rst b/source/elements/oneMKL/source/architecture/other_architecture.inc.rst
@@ -11,12 +11,19 @@ This section covers all other features in the design of oneMKL architecture.
 
 .. _onemkl_spec_current_version:
 
-Version of oneMKL Specification
+Specification Version and Compliance
 +++++++++++++++++++++++++++++++++++++++++++++
 
-This is the oneMKL specification which is part of the oneAPI specification.
+Each oneMKL domain must define a preprocessor macro to represent the version of the specification that the implementation is compliant with.
 
-The implementation must define a macro, `ONEMKL_SPEC_VERSION` as having the numerical value of the specification version.
+The macros for each domain are listed as follows:
+
+  | ONEMKL_BLAS_SPEC_VERSION
+  | ONEMKL_LAPACK_SPEC_VERSION
+  | ONEMKL_SPARSE_SPEC_VERSION
+  | ONEMKL_DFT_SPEC_VERSION
+  | ONEMKL_RNG_SPEC_VERSION
+  | ONEMKL_VM_SPEC_VERSION
 
 The specification version can be created by appending all digits of the specification version in the format of <MAJOR><MINOR>. MINOR version always uses two digits. This version can be used to check the compatibility of the implementation with the specification version.
 
@@ -31,13 +38,13 @@ Macro Example
 .. code-block:: c
 
   // For oneAPI 1.2 rev 1
-  #define ONEMKL_SPEC_VERSION 102
+  #define ONEMKL_BLAS_SPEC_VERSION 102
 
   // For oneAPI 1.2 rev 2
-  #define ONEMKL_SPEC_VERSION 102
+  #define ONEMKL_DFT_SPEC_VERSION 102
 
   // For oneAPI 1.3 rev 1
-  #define ONEMKL_SPEC_VERSION 103
+  #define ONEMKL_VM_SPEC_VERSION 103
 
 
 .. _onemkl_pre_post_conditions: