5.2. CPU Profiling - 5.2. CPU Profiling - 5.3 English - 63856

Some samples may be missed when performing a combined PMC and Timer-based sampling profile run.

If AMD uProf is installed in a path that includes non-ASCII Unicode characters, profiling does not work.

The CPU Profiler does not support profiling of a Windows Store app.

Unsupported instructions such as, VDPBF16PS are shown as BAD DASM in IMIX and Source view.

Occasionally, core PMC samples may not be collected while profiling on KVM guest environment.

On an ESXi guest environment, a high number of samples are collected in comparison to the same application running on a bare-metal system.

Custom profiling with IBS and TBP or EBP events might show zero or fewer samples in the report. To overcome this issue, do not combine - IBS with the other profiling events (TBP or EBP) during the custom profiling.

libclang-cpp.so library bundled with AOCC 3.2 is not CXX11 ABI compliant. AMD uProf OS tracing functionality depends on libclang library (with abi cxx11 support). While running applications compiled with AOCC 3.2, the LD_LIBRARY_PATH points to AOCC 3.2 bin/lib paths and hence, AMD uProf fails giving an undefined symbols error. This issue is not observed if LD_LIBRARY_PATH is not set to AOCC 3.2 libs.

For Java applications running for a long time (more than an hour), the sample data attributed to Java methods might not be accurate.

IBS and MPI profiling are not recommended to be run concurrently as a very large dataset will accumulate.