[GEMM] Set enable-post-misched=0 as default compile option
This PR set "-mllvm -enable-post-misched=0" as default compile option of CK. This option will improve gemm_universal performance and ensure the correctness.
It seems that option doesn't compatible to clang++ in CI codegen test. Hi @illsilin, may I ask the reason behind CI codegen use clang++ compiler? Hi @zjing14 , are our users and customers all use hipcc as compiler?
cc @zjing14
Most of the customers build CK with clang directly and dislike hipcc because it is not transparent about what it does behind the scenes. It is AMD policy to get all rocm components to abandon hipcc and move to clang by 6.2 release. We have started using clang as the default compiler for our builds since November 2023.
Most of the customers build CK with clang directly and dislike hipcc because it is not transparent about what it does behind the scenes. It is AMD policy to get all rocm components to abandon hipcc and move to clang by 6.2 release. We have started using clang as the default compiler for our builds since November 2023.
Thanks for explaining. I tested this branch on ROCm 6.1 and found no problems. It seems that our compiler solved the problem on this version. Is it possible to update the CI docker to ROCm 6.1 which was released today?
We can definitely upgrade our default docker and compiler to rocm6.1, however, it's likely that some customers will continue to use older compiler versions for some time. So I would be a little worried to use compiler flags that will cause build failures with older rocm versions. Perhaps, we can implement these flags as an option in our CI and set the default to ON, instead of hardcoding them in the cmake file?
The 2fix had been merged in PR #1250, so this one is no longer required.