Laurent Morichetti 85fd969253 SWDEV-351980 - Move hip_api_data and record to the HIP function's stack ...

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

2022-09-21 02:41:15 -04:00

hipamd

SWDEV-351980 - Move hip_api_data and record to the HIP function's stack

2022-09-21 02:41:15 -04:00

S

Description

Aucune description fournie

282 MiB

Langue

C++ 67.5%

C 20.6%

Python 6.6%

CMake 3.4%

Shell 0.6%

Autre 1.1%