The AOCL-BLAS library provides optional Debug Tracing and Logging (DTL) functionality. The key features are as follows:
Debug Tracing identifies the code path taken within each API in terms of the function call chain. It prints the information on the internal functions invoked and their order. It is therefore most useful to BLIS developers and those who wish to see the details of low level calls within each BLIS API, down to individual kernel calls. A compile time option is available to control the level of tracing performed.
Debug Logging prints a line for each API call including debugging information, such as values of input parameters. It has a lower overhead than tracing and is recommended for application developers to better understand the usage of BLAS APIs within their code. For selected APIs (
gemm,gemm_compute,gemmt,trsm,nrm2) performance data, such as timing and estimated GFLOPS, is also printed.Each can be separately enabled/disabled at compile time.
When these features are disabled at compile time, they do not require any runtime resources and that does not affect the performance.
All the traces are thread safe, when used from serial programs or MPI and/or OpenMP parallel programs.