472b3f3155130a6a30cd943475f502b3ef7d9f76
Since the hip_api_data and record are only needed at the HIP function's
scope, there is no need to allocate/free them in the ROCtracer activity
callback, they can reside on the HIP function's stack frame.
This solves an issue with the thread local stacks of records the tracer
maintains that are destroyed first (before any global destructor) on
process exit, making it impossible to use HIP functions in global
destructors when the profiler is enabled.
Change-Id: Ib1d70124d009a44dc1f08d41edff95e5f9f84369
[ROCm/clr commit: 85fd969253]
Cur síos
Níor tugadh tuairisc
Teangacha
C++
67.5%
C
20.6%
Python
6.6%
CMake
3.4%
Shell
0.6%
Eile
1.1%