Skip to content

Commit

Permalink
[Docs] Fix errors in example prose
Browse files Browse the repository at this point in the history
* Docs incorrectly state that the example with build for Intel,
contradicting itself later on.
* This error is corrected.
  • Loading branch information
hjabird committed Jul 4, 2024
1 parent d6bd86b commit 975f2d2
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions docs/building_the_project_with_dpcpp.rst
Original file line number Diff line number Diff line change
Expand Up @@ -341,7 +341,7 @@ The following table provides details of CMake options and their default values:
CMake invocation examples
##########################

Build oneMKL with support for x86 CPU, Intel GPU, and Nvidia GPUs with tests
Build oneMKL with support for Nvidia GPUs with tests
disabled using the Ninja build system:

.. code-block:: bash
Expand All @@ -363,7 +363,7 @@ and Intel GPU (``MKLGPU``) backends are enabled by default, but are disabled
here. The backends for Nvidia GPUs must all be explicilty enabled. The tests are
disabled, but the examples will still be built.

Building oneMKL with support x86 CPU, Intel GPU, and AMD GPUs with tests
Building oneMKL with support for AMD GPUs with tests
disabled:

.. code-block:: bash
Expand Down Expand Up @@ -401,7 +401,7 @@ GPU and Nvidia GPU with testing enabled:
Note that this is not a supported configuration, and requires Codeplay's oneAPI
for `AMD <https://developer.codeplay.com/products/oneapi/amd/home/>`_ and
`Nvidia <https://developer.codeplay.com/products/oneapi/nvidia/home/>`_ GPU
plugins. Like the above example, the MKLCPU and MKLGPU backends are enabled by
plugins. The MKLCPU and MKLGPU backends are enabled by
default, with backends for Nvidia GPU and AMD GPU explicitly enabled.
``-DTARGET_DOMAINS=dft`` causes only DFT backends to be built. If this was not
set, the backend libraries to enable the use of BLAS, LAPACK and RNG with MKLGPU
Expand Down

0 comments on commit 975f2d2

Please sign in to comment.