3.1 (revision 12537)
Score-P Tools

scorep

A call to scorep has the following syntax:

This is the Score-P instrumentation tool. The usage is:
scorep <options> <original command>

Common options are:
  --help, -h      Show help output. Does not execute any other command.
  --config=<file> Specifies file for the instrumentation configuration.
  -v, --verbose[=<value>] Specifies the verbosity level. The following
                  levels are available:
                  0 = No output
                  1 = Executed commands are displayed (default if no
                      value is specified)
                  2 = Detailed information is displayed
  --dry-run       Only displays the executed commands. It does not
                  execute any command.
  --keep-files    Do not delete temporarily created files after successful
                  instrumentation. By default, temporary files are deleted
                  if no error occurs during instrumentation.
  --instrument-filter=<file>
                  Specifies the filter file for filtering functions during
                  compile-time. Not supported by all instrumentation methods.
                  It applies the same syntax, as the one used by Score-P during
                  run-time.
  --version       Prints the Score-P version and exits.
  --static        Enforce static linking of the Score-P libraries.
  --dynamic       Enforce dynamic linking of the Score-P libraries.
  --no-as-needed  Adds a GNU ld linker flag to fix undefined references
                  when using shared Score-P libraries. This happens on
                  systems using --as-needed as linker default. It will
                  be handled transparently in future releases of Score-P.
  --thread=<paradigm>[:<variant>]
                  Possible paradigms and variants are:
              none
                  No thread support.
              omp:pomp_tpd
                  OpenMP support using OPARI2 thread tracking.
                  It requires and, thus, automatically enables OPARI2
                  instrumentation.
              omp:ancestry
                  OpenMP support using thread tracking with ancestry functions
                  in OpenMP 3.0 and later.
                  It requires and, thus, automatically enables OPARI2
                  instrumentation.
              pthread
                  Pthread support using thread tracking via library wrapping
                  It conflicts and, thus, automatically disables OPARI2
                  instrumentation.
  --mpp=<paradigm>[:<variant>]
                  Possible paradigms and variants are:
              none
                  No multi-process support.
              mpi
                  MPI support using library wrapping
              shmem
                  SHMEM support using library wrapping
  --mutex=<paradigm>[:<variant>]
                  Possible paradigms and variants are:
              none
                  serial case, no locking
              pthread
                  Pthread mutex locks
              pthread:spinlock
                  Pthread spinlocks
              omp
                  OpenMP locks
  --compiler      Enables compiler instrumentation.
                  By default, it disables pdt instrumentation.
  --nocompiler    Disables compiler instrumentation.
  --cuda          Enables cuda instrumentation.
  --nocuda        Disables cuda instrumentation.
  --online-access Enables online-access support. It is disabled by default
  --noonline-access Disables online-access support.
  --pomp          Enables pomp user instrumentation. By default, it also
                  enables preprocessing.
  --nopomp        Disables pomp user instrumentation. (Default)
  --openmp        Enables instrumentation of OpenMP directives. By default,
                  it also enables preprocessing. (Default for compile units
                  with enabled OpenMP support during the compilation)
  --noopenmp      Disables instrumentation of OpenMP directives.
                  Note: To ensure thread-safe execution of the measurement,
                  parallel regions still need to be tracked and will appear
                  in the results. (Default for compile units without OpenMP
                  enabled compilation)
  --opari=<parameter-list>
                  Pass options to the source-to-source instrumenter OPARI2
                  to have finer control over the instrumentation process.
                  Please refer to the OPARI2 user documentation for more
                  details.
  --pdt[=<parameter-list>]
                  Enables pdt instrumentation.
                  You may add additional parameters that are passed to pdt.
                  It requires and, thus, automatically enables user
                  instrumentation.
                  It conflicts and, thus, automatically disables preprocess
                  instrumentation.
                  By default, it disables compiler instrumentation.
  --nopdt         Disables pdt instrumentation.
  --preprocess    Enables preprocess instrumentation.
                  It cannot be enabled, if not at least one of the following is
                  enabled: OPARI2 instrumentation.
                  It conflicts and, thus, automatically disables pdt
                  instrumentation.
  --nopreprocess  Disables preprocess instrumentation.
  --user          Enables user instrumentation.
  --nouser        Disables user instrumentation.
  --opencl        Enables OpenCL instrumentation.
  --noopencl      Disables OpenCL instrumentation.
  --openacc       Enables OpenACC instrumentation.
  --noopenacc     Disables OpenACC instrumentation.
  --memory        Enables memory usage instrumentation. It is enabled by default.
  --nomemory      Disables memory usage instrumentation.

Report bugs to <support@score-p.org>

scorep-config

A call to scorep-config has the following syntax:

Usage:
scorep-config <command> [<options>]
  Commands:
   --cflags    prints additional compiler flags for a C compiler. They already
               contain the include flags.
   --cxxflags  prints additional compiler flags for a C++ compiler. They already
               contain the include flags.
   --fflags    prints additional compiler flags for a Fortran compiler. They already
               contain the include flags.
   --cppflags[=language]
               prints the include flags. They are already contained in the
               output of the --cflags, --cxxflags, and --fflags commands.
               language may be one of c (default), c++, or fortran
   --ldflags   prints the library path flags for the linker
   --libs      prints the required linker flags
   --cc        prints the C compiler name
   --cxx       prints the C++ compiler name
   --fc        prints the Fortran compiler name
   --mpicc     prints the MPI C compiler name
   --mpicxx    prints the MPI C++ compiler name
   --mpifc     prints the MPI Fortran compiler name
   --help      prints this usage information
   --version   prints the version number of the Score-P package
   --scorep-revision prints the revision number of the Score-P package
   --common-revision prints the revision number of the common package
   --remap-specfile  prints the path to the remapper specification file
  Options:
   --nvcc      Convert flags to be suitable for the nvcc compiler.
   --static    Use only static Score-P libraries if possible.
   --dynamic   Use only dynamic Score-P libraries if possible.
   --online-access|--noonline-access
            Specifies whether online access (needed by Periscope) is enabled.
            On default it is enabled.
   --compiler|--nocompiler
            Specifies whether compiler instrumentation is used.
            On default compiler instrumentation is enabled.
   --user|--nouser
            Specifies whether user instrumentation is used.
            On default user instrumentation is disabled.
   --pomp|--nopomp
            Specifies whether pomp instrumentation is used.
            On default pomp instrumentation is disabled.
   --cuda|--nocuda
            Specifies whether cuda instrumentation is used.
            On default cuda instrumentation is enabled.
   --openacc|--noopenacc
            Specifies whether openacc instrumentation is used.
            On default openacc instrumentation is enabled.
   --opencl|--noopencl
            Specifies whether opencl instrumentation is used.
            On default opencl instrumentation is enabled.
   --preprocess|--nopreprocess
            Specifies whether preprocess instrumentation is used.
            On default preprocess instrumentation is disabled.
   --memory=<memory-api-list>|--nomemory
            Specifies whether memory usage recording is used.
            On default memory usage recording is enabled.
            The following memory interfaces may be recorded:
             libc:
              malloc,realloc,calloc,free,memalign,posix_memalign,valloc
             libc11:
              aligned_alloc
             c++L32|c++L64:
              new,new[],delete,delete[] (IA-64 C++ ABI)
             pgCCL32|pgCCL64:
              new,new[],delete,delete[] (old PGI/EDG C++ ABI)
   --thread=<threading system>[:<variant>]
            Available threading systems are:
         none   This is the default.
         omp:pomp_tpd
         omp:ancestry
         pthread
            If no variant is specified the first matching
            threading system is used.
   --mutex=<locking system>[:<variant>]
            Available locking systems are:
         none
         omp
         pthread
         pthread:spinlock
         pthread:wrap
            If no variant is specified the default for the respective
            threading system is used.
   --mpp=<multi-process paradigm>
            Available multi-process paradigms are:
         mpi    This is the default.
         shmem
         none

Report bugs to <support@score-p.org>

scorep-info

A call to scorep-info has the following syntax:

Usage: scorep-info <info command> <command options>
       scorep-info --help
This is the Score-P info tool.

Available info commands:

  config-vars:
    Shows the list of all measurement config variables with a short description.

    Info command options:
      --help        Displays a description of the Score-P measurement configuration system.
      --full        Displays a detailed description for each config variable.
      --values      Displays the current values for each config variable.
                    Warning: These values may be wrong, please consult the
                             manual of the batch system how to pass the values
                             to the measurement job.

  config-summary:
    Shows the configure summary of the Score-P package.

  open-issues:
    Shows open and known issues of the Score-P package.

Report bugs to <support@score-p.org>

scorep-score

A call to scorep-score has the following syntax:

Usage: scorep-score <profile> [options]
Options:
 -r          Show all regions.
 -h, --help  Show this help and exit.
 -f <filter> Shows the result with the filter applied.
 -c <num>    Specifes the number of hardware counters that shall be measured.
             By default, this value is 0, which means that only a timestamp
             is measured on each event. If you plan to record hardware counters
             specify the number of hardware counters. Otherwise, scorep-score
             may underestimate the required space.
 -m          Prints mangled region names instead of demangled names.

scorep-backend-info

Note
This tool is intended to run as a batch job. Please consult the manual of the batch system how to submit jobs.

A call to scorep-backend-info has the following syntax:

Usage: scorep-backend-info <info command> <command options>
       scorep-backend-info --help
This is the Score-P backend info tool.

Available info commands:

  system-tree:
    Shows the available system tree levels, starting with the root.

  config-vars:
    Shows the current values of all measurement config variables.

Report bugs to <support@score-p.org>