From 1ea4bda577f23247273456dbf72cc6d89ee1730b Mon Sep 17 00:00:00 2001 From: "Malia, Viraj" Date: Tue, 3 Sep 2024 09:19:08 -0700 Subject: [PATCH] Fix formatting --- .../architecture/other_architecture.inc.rst | 20 ++++++++++--------- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/source/elements/oneMKL/source/architecture/other_architecture.inc.rst b/source/elements/oneMKL/source/architecture/other_architecture.inc.rst index b5585495fe..50678e6c24 100644 --- a/source/elements/oneMKL/source/architecture/other_architecture.inc.rst +++ b/source/elements/oneMKL/source/architecture/other_architecture.inc.rst @@ -21,20 +21,22 @@ The implementation must define a macro, `ONEMKL_SPEC_VERSION` as having the nume The specification version can be created by appending all digits of the specification version in the format of . MINOR version always uses two digits. This version can be used to check the compatibility of the implementation with the specification version. Version Example -oneAPI 1.1 rev 1 will be represented as a numerical value of 101 -oneAPI 1.2 rev 1 will be represented as a numerical value of 102 -oneAPI 1.2 rev 2 will be represented as a numerical value of 102 + | oneAPI 1.1 rev 1 will be represented as a numerical value of 101 + | oneAPI 1.2 rev 1 will be represented as a numerical value of 102 + | oneAPI 1.2 rev 2 will be represented as a numerical value of 102 Macro Example -// For oneAPI 1.2 rev 1 -#define ONEMKL_SPEC_VERSION 102 +.. code-block:: c -// For oneAPI 1.2 rev 2 -#define ONEMKL_SPEC_VERSION 102 + // For oneAPI 1.2 rev 1 + #define ONEMKL_SPEC_VERSION 102 -// For oneAPI 1.3 rev 1 -#define ONEMKL_SPEC_VERSION 103 + // For oneAPI 1.2 rev 2 + #define ONEMKL_SPEC_VERSION 102 + + // For oneAPI 1.3 rev 1 + #define ONEMKL_SPEC_VERSION 103 .. _onemkl_pre_post_conditions: