Evgeny Mankov

[HIPIFY][clang] Add a callback in clang to decide on hipify-clang's side whether to exclude the particular false conditional block or not

1

With the change https://github.com/ROCm-Developer-Tools/HIP/pull/1372, all the blocks are not excluded from AST when `-skip-excluded-preprocessor-conditional-blocks` option is set. The corresponding change in clang: https://reviews.llvm.org/D66597. The main idea is: if there is...

**[IMP]** `int64_t` rocBLAS APIs should be available in the same compilation unit. That means, `int`-based APIs can `live` in the same code simultaneously with `int64_t` ones. For instance: ```cpp cublasStatus_t...

**[Reason]** + To cover ABI changes, when the signature of an API is changed, and the name is left the same. **[Example]** hipBLAS function `hipblasStrmm` Before 6.0.0: ```cpp HIPBLAS_DEPRECATED_MSG("hipblasStrmm with...

+ If `--use-hip-data-types` is set (unset by default), always convert `cudaDataType_t` to `hipDataType` for all HIP libs (ROC libs - to investigate) + If `--use-hip-data-types` is unset (by default) convert...

**[ToDo]** + Add new markers `CUDA_C`, `CUDA_CPP`, `HIP_C`, `HIP_CPP`, maybe `ROC_C` and `ROC_CPP` as well to the API matching entities, where we have such information + If the above additional...

**[Synopsis]** + Currently, only `1-to-1` unconditional matchers are presented in hipify-clang **[ToDo]** + If the signature of a particular API function changed or there are multiple APIs with the same...

It might be done by throwing a warning message with `line:col` information for each inline assembler occurrence

The rocSOLVER lives here: https://github.com/ROCmSoftwarePlatform/rocSOLVER, it is alive and synced with HIP releases.

+ Implement `rocFFT` support analogically to `rocBLAS`