Using the rocsys command#
rocsys is the unified command-line entry point for ROCm Systems Profiler.
A subcommand selects the tool. Flags after the subcommand are forwarded to that
tool, including --help.
The existing rocprof-sys-* executables remain available and behave as before.
Use them directly when a workflow page shows that command, or use the matching
rocsys verb below.
Usage#
rocsys -- ./app
rocsys profile -- ./app
rocsys <subcommand> [options] -- <app> [app-args]
rocsys --help
rocsys <subcommand> --help
rocsys with no arguments prints the top-level help. rocsys --version
prints the version.
Subcommands#
Verb |
Runs |
See also |
|---|---|---|
|
A full trace profile through |
Using preset profiles and domain flags, Instrumenting and rewriting a binary application |
|
Runtime instrumentation through |
|
|
Binary rewrite through |
|
|
|
|
|
|
|
|
|
|
|
|
These two forms collect the same full trace profile:
rocsys -- ./app
rocsys profile -- ./app
rocsys profile with no application exits with an error. Pass --help to
read the rocprof-sys-run options, including presets:
rocsys profile --help
rocsys profile --preset=balanced -- ./app
Default output for rewrite#
rocsys rewrite -- ./app runs rocprof-sys-instrument -o -- ./app. When
-o has no filename, the rewritten file is written in the current directory:
Target |
Default output |
|---|---|
|
|
A name with no extension, such as |
|
A library already in the current directory, such as |
|
A target outside the current directory, such as |
|
A target is treated as a library only when its basename contains a dot and either
starts with lib, contains .so, or ends with .a.
Pass -o, --output, or -o= to choose the path yourself:
rocsys rewrite -o app.inst -- ./app
Call-stack sampling#
rocsys sample is not a subcommand and reports an unknown subcommand.
Enable call-stack sampling while profiling with --sample:
rocsys --sample -- ./my_app
rocsys profile --sample -- ./my_app