From f13ee7af7e9784aff285bc27641d1e4b839af2ff Mon Sep 17 00:00:00 2001 From: Jan Siwiec <jan.siwiec@vsb.cz> Date: Wed, 15 Apr 2020 10:53:23 +0200 Subject: [PATCH] Update aislinn.md --- docs.it4i/software/debuggers/aislinn.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs.it4i/software/debuggers/aislinn.md b/docs.it4i/software/debuggers/aislinn.md index 127b89a1a..4241e1072 100644 --- a/docs.it4i/software/debuggers/aislinn.md +++ b/docs.it4i/software/debuggers/aislinn.md @@ -83,7 +83,7 @@ At the beginning of the report, there are some basic summaries of the verificati It shows us: -* Error occurs in process 0 in test.cpp on line 16. +* Error occurs in process 0 in `test.cpp` on line 16. * Stdout and stderr streams are empty. (The program does not write anything). * The last part shows MPI calls for each process that occurs in the invalid run. More detailed information about each call can be obtained by hovering the mouse cursor over the respective MPI call. @@ -98,7 +98,7 @@ Since the verification is a non-trivial process, there are some of limitations. There are also some limitations bounded to the current version and they will be removed in the future: * All files containing MPI calls have to be recompiled by MPI implementation provided by Aislinn. The files that do not contain MPI calls, do not have to be recompiled. Aislinn MPI implementation supports many commonly used calls from MPI-2 and MPI-3 related to point-to-point communication, collective communication, and communicator management. Unfortunately, MPI-IO and one-side communication is not implemented yet. -* Each MPI can use only one thread (if you use OpenMP, set OMP_NUM_THREADS to 1). +* Each MPI can use only one thread (if you use OpenMP, set `OMP_NUM_THREADS` to 1). * There are some limitations for using files, but if the program just reads inputs and writes results, it is OK. [a]: http://verif.cs.vsb.cz/aislinn/ -- GitLab