c56dcb6ffb
The environment variable AOCL_VERBOSE was inconsistent in its behaviour, sometimes producing a single line of output per file from multiple BLAS calls, when it should be all or nothing. Note that: - AOCL_VERBOSE is only active when DTL logging has been enabled at compile time. Otherwise, this environment variable is not read. - When logging is enable at compile time, logging output is produced by default. Thus AOCL_VERBOSE is more of use to turn output off, rather than on. - For production runs without logging, it is recommended to recompile with DTL disabled, as this minimizes overheads within the BLIS code. - AOCL_VERBOSE should be set to 0 or 1, and not values such as FALSE or TRUE. Changes to improve consistency when AOCL_VERBOSE is set: - Change DTL variables from Bool (unsigned char) datatype to bool, as used elsewhere in BLIS. - Ensure bli_init_auto() is called before AOCL_DTL_TRACE_ENTRY() and AOCL_DTL_LOG_*_INPUTS(), as bli_init_auto calls AOCL_DTL_INITIALIZE() - In APIs which avoid calling bli_init_auto(), add explicit calls to AOCL_DTL_INITIALIZE(). Also, make a proper comment about not calling bli_init_auto(), rather than just commenting out call, which looks like dead code. Other DTL logging control changes: - Make gbIsLoggingEnabled ICV thread local as this can be updated by calls to AOCL_DTL_Enable_Logs and AOCL_DTL_Disable_Logs APIs - After recent changes to hide some internal BLIS definitions behind ifdef BLIS_IS_BUILDING_LIBRARY guard, change BLIS_THREAD_LOCAL definition to be exported again. Logging output changes: - Standardize printing of datatype to be lower case. - Don't force printing of GEMM transa and transb to upper case, instead print in the case provided by the application code. - Add logging output to all variants (in terms of AMD/non-AMD optimized and datatype) of SWAP and SCAL. AMD-Internal: [CPUPL-7010]
AOCL-BLAS library
AOCL-BLAS is AMD's optimized version of BLAS targeted for AMD EPYC and Ryzen CPUs. It is developed as a forked version of BLIS (https://github.com/flame/blis), which is developed by members of the Science of High-Performance Computing (SHPC) group in the Institute for Computational Engineering and Sciences at The University of Texas at Austin and other collaborators (including AMD). All known features and functionalities of BLIS are retained and supported in AOCL-BLAS library. AOCL-BLAS is regularly updated with the improvements from the upstream repository.
AOCL BLAS is optimized with SSE2, AVX2, AVX512 instruction sets which would be enabled based on the target Zen architecture using the dynamic dispatch feature. All prominent Level 3, Level 2 and Level 1 APIs are designed and optimized for specific paths targeting different size spectrums e.g., Small, Medium and Large sizes. These algorithms are designed and customized to exploit the architectural improvements of the target platform.
For detailed instructions on how to configure, build, install, and link against AOCL-BLAS on AMD CPUs, please refer to the AOCL User Guide located on AMD developer portal.
The upstream repository (https://github.com/flame/blis) contains further information on BLIS, including background information on BLIS design, usage examples, and a complete BLIS API reference.
AOCL-BLAS is developed and maintained by AMD. You can contact us on the email-id toolchainsupport@amd.com. You can also raise any issue/suggestion on the git-hub repository at https://github.com/amd/blis/issues.