From 9b64d7684d32ed2bdc4e63eb52491a2a80df6470 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Luk=C3=A1=C5=A1=20Krup=C4=8D=C3=ADk?= <lukas.krupcik@vsb.cz> Date: Mon, 20 Sep 2021 13:50:47 +0200 Subject: [PATCH] Update docs.it4i/software/intel/intel-suite/intel-integrated-performance-primitives.md Deleted docs.it4i/software/intel/intel-suite/intel-debugger.md --- .../intel/intel-suite/intel-debugger.md | 80 ------------------- ...intel-integrated-performance-primitives.md | 11 +-- 2 files changed, 2 insertions(+), 89 deletions(-) delete mode 100644 docs.it4i/software/intel/intel-suite/intel-debugger.md diff --git a/docs.it4i/software/intel/intel-suite/intel-debugger.md b/docs.it4i/software/intel/intel-suite/intel-debugger.md deleted file mode 100644 index 310b118be..000000000 --- a/docs.it4i/software/intel/intel-suite/intel-debugger.md +++ /dev/null @@ -1,80 +0,0 @@ -# Intel Debugger - -!!! note - IDB is no longer available since Intel Parallel Studio 2015. - -## Introduction - -The Intel debugger version is available via the `intel/13.5.192` module. The debugger works for serial and parallel applications compiled with the C and C++ compiler and the ifort Fortran 77/90/95 compiler. The debugger provides a Java GUI environment. Use [X display][1] to run the GUI. - -```console -$ ml intel/13.5.192 -$ ml Java -$ idb -``` - -The debugger may run in text mode. To debug in the text mode, use: - -```console -$ idbc -``` - -To debug on compute nodes, the `intel` module must be loaded. The GUI on compute nodes may be accessed using the same way as in the [GUI section][1]. - -## Debugging Serial Applications - -Example: - -```console -$ qsub -q qexp -l select=1:ncpus=24 -X -I - qsub: waiting for job 19654.srv11 to start - qsub: job 19654.srv11 ready -$ ml intel -$ ml Java -$ icc -O0 -g myprog.c -o myprog.x -$ idb ./myprog.x -``` - -In this example, we allocate 1 full compute node, compile the myprog.c program with the `-O0 -g` debugging options and run the IDB debugger interactively on the myprog.x executable. The GUI access is via the X11 port forwarding provided by the PBS workload manager. - -## Debugging Parallel Applications - - The Intel debugger is capable of debugging multithreaded and MPI parallel programs as well. - -### Small Number of MPI Ranks - -For debugging small number of MPI ranks, you may execute and debug each rank in a separate xterm terminal (do not forget the [X display][1]. Using Intel MPI, this may be done in the following way: - -```console -$ qsub -q qexp -l select=2:ncpus=24 -X -I - qsub: waiting for job 19654.srv11 to start - qsub: job 19655.srv11 ready -$ ml intel -$ mpirun -ppn 1 -hostfile $PBS_NODEFILE --enable-x xterm -e idbc ./mympiprog.x -``` - -In this example, we allocate 2 full compute nodes, run xterm on each node, and start the IDB debugger in the command line mode, debugging two ranks of the mympiprog.x application. The xterm will pop up for each rank with IDB prompt ready. The example is not limited to use of Intel MPI. - -### Large Number of MPI Ranks - -Run the IDB debugger from within the MPI debug option. This will cause the debugger to bind to all ranks and provide aggregated outputs across the ranks, pausing execution automatically just after startup. You may then set break points and step the execution manually. Using Intel MPI: - -```console -$ qsub -q qexp -l select=2:ncpus=24 -X -I - qsub: waiting for job 19654.srv11 to start - qsub: job 19655.srv11 ready -$ ml intel -$ mpirun -n 48 -idb ./mympiprog.x -``` - -### Debugging Multithreaded Application - -Run the IDB debugger in GUI mode. The Parallel menu contains a number of tools for debugging multiple threads. One of the most useful tools is the **Serialize Execution** tool, which serializes execution of concurrent threads for easy orientation and identification of concurrency related bugs. - -## Further Information - -Exhaustive manual on IDB features and usage is published at the [Intel website][a]. - -[1]: ../../../general/accessing-the-clusters/graphical-user-interface/x-window-system.md - -[a]: https://software.intel.com/sites/products/documentation/doclib/iss/2013/compiler/cpp-lin/ diff --git a/docs.it4i/software/intel/intel-suite/intel-integrated-performance-primitives.md b/docs.it4i/software/intel/intel-suite/intel-integrated-performance-primitives.md index 572d93360..c79bff525 100644 --- a/docs.it4i/software/intel/intel-suite/intel-integrated-performance-primitives.md +++ b/docs.it4i/software/intel/intel-suite/intel-integrated-performance-primitives.md @@ -12,11 +12,6 @@ For the current list of installed versions, use: $ ml av ipp ``` -!!! Important - Check out IPP before implementing own math functions for data processing, as it is likely already there. - IPP version 9.0.1 compiled for AVX2 vector instructions is available via the `ipp` module: - The module sets up environment variables, required for linking and running IPP-enabled applications. - ## IPP Example ```cpp @@ -63,16 +58,14 @@ int main(int argc, char* argv[]) Compile the example above, using any compiler and the `ipp` module: ```console -$ ml intel -$ ml ipp +$ ml intel/2020b ipp/2020.3.304 $ icc testipp.c -o testipp.x -lippi -lipps -lippcore ``` You will need the `ipp` module loaded to run an IPP-enabled executable. This may be avoided, by compiling library search paths into the executable: ```console -$ ml intel -$ ml ipp +$ ml intel/2020b ipp/2020.3.304 $ icc testipp.c -o testipp.x -Wl,-rpath=$LIBRARY_PATH -lippi -lipps -lippcore ``` -- GitLab