 |
1.4.2 (revision 8839)
|
|
1.4.2 (revision 8839)
|
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 successfull
instrumentation. By default, temporary files are deleted
if no error occures 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 opari instrumentation.
omp:ancestry
OpenMP support using thread tracking with ancestry functions in OpenMP 3.0 and later
It requires and, thus, automatically enables opari instrumentation.
pthread
Pthread support using thread tracking via library wrapping
It conflicts and, thus, automatically disables opari 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 online-access Disables online-access support.
--pomp[=<parameter-list>]
Enables pomp user instrumentation.
You may add additional parameters that are passed to OPARI2.
By default, it enables also preprocessing
--nopomp Disables pomp user instrumentation.
--opari[=<parameter-list>]
Enables OPARI2 instrumentation of OpenMP regions.
You may add additional parameters that are passed to OPARI2
By default, it enables also preprocessing and
pomp user instrumentation.
--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 requires and, thus, automatically enables opari 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.
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 prints the include flags. They are already contained in the
output of the --cflags, --cxxflags, and --fflags commands
--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.
--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.
--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
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:
--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.
A call to scorep-score has the following syntax:
Usage: scorep-score <profile> [options]
Options:
-r Show all regions.
-h 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 if available.
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.