diff --git a/docs/_include_files/env_setup_gsg.rst b/docs/_include_files/env_setup_gsg.rst index 63cd671ec9e9..dc4527808eb7 100644 --- a/docs/_include_files/env_setup_gsg.rst +++ b/docs/_include_files/env_setup_gsg.rst @@ -19,4 +19,4 @@ To configure the |tool_name| environment, set the following environment variable If you use the |dpcpp_compiler|, make sure to `set environment variables using -the setvars script `_. \ No newline at end of file +the setvars script `_. \ No newline at end of file diff --git a/docs/dev_guide/migration/migration-workflow.rst b/docs/dev_guide/migration/migration-workflow.rst index ef09e7faaf4b..bf34034c6745 100644 --- a/docs/dev_guide/migration/migration-workflow.rst +++ b/docs/dev_guide/migration/migration-workflow.rst @@ -113,7 +113,7 @@ This signature will be used later for validation after migration. Enable CodePin with the ``–enable-codepin`` option. For detailed information about debugging using the CodePin tool, refer to -`Debug Migrated Code Runtime Behavior `_. +`Debug Migrated Code Runtime Behavior `_. Configure the Tool ****************** @@ -425,7 +425,7 @@ project signature will be logged during the execution time. The signature contains the data value of each execution checkpoint, which can be verified manually or with an auto-analysis tool. For detailed information about debugging using the CodePin tool, refer to -`Debug Migrated Code Runtime Behavior `_. +`Debug Migrated Code Runtime Behavior `_. Optimize Your Code ------------------ @@ -437,7 +437,7 @@ code to improve for optimizing your application performance. Additional hardware- or library-specific optimization information is available: * For detailed information about optimizing your code for Intel GPUs, refer to - the `oneAPI GPU Optimization Guide `_. + the `oneAPI GPU Optimization Guide `_. * For detailed information about optimizing your code for AMD GPUs, refer to the `Codeplay AMD GPU Performance Guide `_. * For detailed information about optimizing your code for NVIDIA GPUS, refer to diff --git a/docs/dev_guide/reference/diagnostic_ref/dpct1033.rst b/docs/dev_guide/reference/diagnostic_ref/dpct1033.rst index 2a5d7f1600de..f833563ad614 100644 --- a/docs/dev_guide/reference/diagnostic_ref/dpct1033.rst +++ b/docs/dev_guide/reference/diagnostic_ref/dpct1033.rst @@ -27,7 +27,7 @@ Suggestions to Fix Set user-defined direction numbers to the basic Sobol generator and use it as Scrambled Sobol generator. -See the `Random Number Generators `_ topic for more information. +See the `Random Number Generators `_ topic for more information. For example, this original CUDA\* code: diff --git a/docs/dev_guide/reference/diagnostic_ref/dpct1036.rst b/docs/dev_guide/reference/diagnostic_ref/dpct1036.rst index f3839934f437..4fcf936c4d1a 100644 --- a/docs/dev_guide/reference/diagnostic_ref/dpct1036.rst +++ b/docs/dev_guide/reference/diagnostic_ref/dpct1036.rst @@ -28,4 +28,4 @@ Suggestions to Fix Rewrite this code manually by using a supported random number generator. -See the `Random Number Generators `_ topic for more information. +See the `Random Number Generators `_ topic for more information. diff --git a/docs/dev_guide/reference/diagnostic_ref/dpct1045.rst b/docs/dev_guide/reference/diagnostic_ref/dpct1045.rst index 02d2bdd7626e..7d5bbfec6178 100644 --- a/docs/dev_guide/reference/diagnostic_ref/dpct1045.rst +++ b/docs/dev_guide/reference/diagnostic_ref/dpct1045.rst @@ -24,7 +24,7 @@ Suggestions to Fix If the matrix type in used is: * Supported by the routine: ignore this warning. -* Not supported by the routine: manually fix the code according to `sparse-blas-routines `_. +* Not supported by the routine: manually fix the code according to `sparse-blas-routines `_. For example, this original CUDA\* code: diff --git a/docs/dev_guide/reference/diagnostic_ref/dpct1046.rst b/docs/dev_guide/reference/diagnostic_ref/dpct1046.rst index 61319b7cc0c1..d8e0430a8978 100644 --- a/docs/dev_guide/reference/diagnostic_ref/dpct1046.rst +++ b/docs/dev_guide/reference/diagnostic_ref/dpct1046.rst @@ -30,7 +30,7 @@ Use a supported data type to rewrite the code. Suggestions to Fix ------------------ -Please refer to the `gemm topic `_ +Please refer to the `gemm topic `_ of the Intel® oneAPI Math Kernel Library (oneMKL) - Data Parallel C++ Developer Reference for supported data types to fix the code manually. diff --git a/docs/dev_guide/reference/diagnostic_ref/dpct1071.rst b/docs/dev_guide/reference/diagnostic_ref/dpct1071.rst index 906e80db6404..f6a7170ae2ff 100644 --- a/docs/dev_guide/reference/diagnostic_ref/dpct1071.rst +++ b/docs/dev_guide/reference/diagnostic_ref/dpct1071.rst @@ -34,4 +34,4 @@ If the placement is incorrect, you may need to manually add the necessary ``set_ statements before the call to ``commit()``. Refer to the -`descriptor::set_value function `_ for more information. \ No newline at end of file +`descriptor::set_value function `_ for more information. \ No newline at end of file diff --git a/docs/dev_guide/reference/diagnostic_ref/dpct1075.rst b/docs/dev_guide/reference/diagnostic_ref/dpct1075.rst index 66a68c3f5991..c48463e34595 100644 --- a/docs/dev_guide/reference/diagnostic_ref/dpct1075.rst +++ b/docs/dev_guide/reference/diagnostic_ref/dpct1075.rst @@ -71,4 +71,4 @@ correctly and are using the correct queue parameter. Fix the code if needed by adding missing commit calls and adjusting queue parameters. Refer to the -`descriptor::commit function `_ for more information. +`descriptor::commit function `_ for more information. diff --git a/docs/dev_guide/reference/diagnostic_ref/dpct1110.rst b/docs/dev_guide/reference/diagnostic_ref/dpct1110.rst index 06b17ea9fbc9..03cb84f7cbb6 100644 --- a/docs/dev_guide/reference/diagnostic_ref/dpct1110.rst +++ b/docs/dev_guide/reference/diagnostic_ref/dpct1110.rst @@ -26,7 +26,7 @@ local variable size in a device function exceeds 128 bytes, some variables may b stored in local or global memory, potentially leading to reduced performance when frequently accessed. To address this issue, you can either decrease the sub-group size to make more registers available for each work-item, or follow the recommendations -in the `Optimizing Register Spills `_ section of the oneAPI GPU +in the `Optimizing Register Spills `_ section of the oneAPI GPU Optimization Guide. For other hardware, please consult with your hardware vendor to get configuration information.