This chapter provides some information on using QMCPACK with external tools.
LLVM Sanitizer Libraries¶
Using CMake, set one of these flags for using the clang sanitizer libraries with or without lldb.
-DLLVM_SANITIZE_ADDRESS link with the Clang address sanitizer library -DLLVM_SANITIZE_MEMORY link with the Clang memory sanitizer library
These set the basic flags required to build with either of these sanitizer libraries. They require a build of clang with dynamic libraries somehow visible (i.e., through
LD_FLAGS=-L/your/path/to/llvm/lib). You must link through clang, which is generally the default when building with it. Depending on your system and linker, this may be incompatible with the “Release” build, so set
-DCMAKE_BUILD_TYPE=Debug. They have been tested with the default spack install of llvm 7.0.0 and been manually built with llvm 7.0.1. See the following links for additional information on use, run time, and build options of the sanitizers: https://clang.llvm.org/docs/AddressSanitizer.html & https://clang.llvm.org/docs/MemorySanitizer.html.
In general, the address sanitizer libraries will catch most pointer-based errors. ASAN can also catch memory links but requires that additional options be set. MSAN will catch more subtle memory management errors but is difficult to use without a full set of MSAN-instrumented libraries.
Intel’s VTune profiler has an API that allows program control over collection (pause/resume) and can add information to the profile data (e.g., delineating tasks).
If the variable
USE_VTUNE_API is set, QMCPACK will check that the
include file (
ittnotify.h) and the library (
libittnotify.a) can be found.
To provide CMake with the VTune search paths, add
VTUNE_ROOT which contains
An example of options to be passed to CMake:
-DUSE_VTUNE_API=ON \ -DVTUNE_ROOT=/opt/intel/vtune_amplifier_xe
Timers as Tasks¶
To aid in connecting the timers in the code to the profile data, the start/stop of
timers will be recorded as a task if
USE_VTUNE_TASKS is set.
In addition to compiling with
USE_VTUNE_TASKS, an option needs to be set at run time to collect the task API data.
In the graphical user interface (GUI), select the checkbox labeled “Analyze user tasks” when setting up the analysis type.
For the command line, set the
enable-user-tasks knob to
true. For example,
amplxe-cl -collect hotspots -knob enable-user-tasks=true ...
Collection with the timers set at “fine” can generate too much task data in the profile. Collection with the timers at “medium” collects a more reasonable amount of task data.
NVIDIA Tools Extensions¶
NVIDIA’s Tools Extensions (NVTX) API enables programmers to annotate their source code when used with the NVIDIA profilers.
If the variable
USE_NVTX_API is set, QMCPACK will add the library (
libnvToolsExt.so) to the QMCPACK target. To add NVTX annotations
to a function, it is necessary to include the
nvToolsExt.h header file and then make the appropriate calls into the NVTX API. For more information
about the NVTX API, see https://docs.nvidia.com/cuda/profiler-users-guide/index.html#nvtx. Any additional calls to the NVTX API should be guarded by
USE_NVTX_API compiler define.
Scitools Understand (https://scitools.com/) is a tool for static code analysis. The easiest configuration route is to use the JSON output from CMake, which the Understand project importer can read directly:
Configure QMCPACK by running CMake with
CMAKE_EXPORT_COMPILE_COMMANDS=ON, for example:
cmake -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ -DQMC_MPI=0 -DCMAKE_EXPORT_COMPILE_COMMANDS=ON ../qmcpack/
Run Understand and create a new C++ project. At the import files and settings dialog, import the
compile_commands.jsoncreated by CMake in the build directory.