You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/README.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,15 +3,14 @@ oneAPI Math Kernel Library (oneMKL) Interfaces offers examples with the followin
3
3
- blas: level3/gemm_usm
4
4
- rng: uniform_usm
5
5
- lapack: getrs_usm
6
-
- dft: complex_fwd_buffer, real_fwd_usm
6
+
- dft: complex_fwd_usm, real_fwd_usm
7
7
- sparse_blas: sparse_gemv_usm
8
8
9
9
Each routine has one run-time dispatching example and one compile-time dispatching example (which uses both mklcpu and cuda backends), located in `example/<$domain>/run_time_dispatching` and `example/<$domain>/compile_time_dispatching` subfolders, respectively.
10
10
11
11
To build examples, use cmake build option `-DBUILD_EXAMPLES=true`.
12
12
Compile_time_dispatching will be built if `-DBUILD_EXAMPLES=true` and cuda backend is enabled, because the compile-time dispatching example runs on both mklcpu and cuda backends.
13
13
Run_time_dispatching will be built if `-DBUILD_EXAMPLES=true` and `-DBUILD_SHARED_LIBS=true`.
14
-
All DFT examples require the mklgpu backend to be enabled.
15
14
16
15
The example executable naming convention follows `example_<$domain>_<$routine>_<$backend>` for compile-time dispatching examples
17
16
or `example_<$domain>_<$routine>` for run-time dispatching examples.
0 commit comments