Score-P

When using ScoreP the configure or cmake command should be prefixed with SCOREP_WRAPPER=off, and the compiler names should be prefixed with scorep-. For an Intel toolchain with autotools this looks like:

SCOREP_WRAPPER=off ./configure CC=scorep-icx CXX=scorep-icpx ...

<<<<<<< HEAD

Score-P variants

If we use scripts alike scorep-icx, we implicitly assume that Score-P has been built against the Intel compiler. If you install it manually on your system, this might not be the default, i.e. Score-P might be built again GNU. To toggle this behaviour, ensure you configure Score-P with

    ./configure --with-nocross-compiler-suite=oneapi

======= The instruction above assumes that Score-P's module files are built such that they provide scripts alike scorep-icx. If such a script does not exist, you might have built Scalasca without the Intel compiler even though you want to use the Intel compiler (default it GNU). If so, add

       --with-nocross-compiler-suite=oneapi

to your configure call.

‍refs/remotes/origin/infrastructure

Logging against Score-P

Please consult Logging, tracing, statistics, profiling and assertions on some information how to pick proper logging outputs (devices) for a build with Score-P. Using this logger ensures that the trace and profile builds of Peano dump their output into an API that helps Score-P to augment its traces. Otherwise, these outputs just go to the terminal.

MAQAO

When using any performance analysis tool the compilation flag "-g" should be used, to generate debug information. For MAQAO this may not be sufficient, in which case "-grecord-gcc-switches" should also be used.

MAQAO reports can be generated on login nodes using

maqao oneview -R1 -- ./program

or on compute nodes using

maqao oneview -R1 --mpi-command="srun -p <partition_name> -A <account> -t <time>" -- ./program

Find a reference guide at https://www.maqao.org/documentation/MAQAO_QuickReferenceSheet.pdf

Table of Contents

Score-P

Score-P variants

Logging against Score-P

MAQAO