ck:profiler:remove gfx macros

[yingluAMD]

Proposed changes

CKProfiler files are actually CPU code. __gfx macros doesn't work. Remove them and use CK_ENABLE_TF32 control whether enroll this datatypes compilation.

Checklist

Please put an x into the boxes that apply. You can also fill these out after creating the PR. If you're not sure, please don't hesitate to ask.

• I have added tests relevant to the introduced functionality, and the unit tests are passing locally
• I have added the test to REGRESSION_TESTS list defined at the top of CMakeLists.txt in tests/CMakeLists.txt, IF the test takes more than 30 seconds to run.
• I have added inline documentation which enables the maintainers with understanding the motivation
• I have removed the stale documentation which is no longer relevant after this pull request
• (If this change is user-facing) I have added release notes which provide the end users with a brief summary of the improvement from this pull request
• I have run clang-format on all changed files
• Any dependent changes have been merged

Discussion

[illsilin]

Well, you're not actually removing any of the gfx macros, you're just replacing the individual ones like gfx942 or gfx950 with a combined one, gfx9, which gets defined when any of the gfx908, gfx90a, gfx942, or gfx950 are defined. So I'm not sure whether these changes will have the desired effect. Have you actually verified them? Are you able to run ckProfiler with tf32 convolutions on any of the gfx9xx devices with these changes?

[yingluAMD]

Well, you're not actually removing any of the gfx macros, you're just replacing the individual ones like gfx942 or gfx950 with a combined one, gfx9, which gets defined when any of the gfx908, gfx90a, gfx942, or gfx950 are defined. So I'm not sure whether these changes will have the desired effect. Have you actually verified them? Are you able to run ckProfiler with tf32 convolutions on any of the gfx9xx devices with these changes?

Yes. __gfx9__ has same scope as __gfx942__ & __gfx950__. It doesn't work on CPU code also. After removing **gfx** macros, ckProfiler build fail on gfx110x. Because TF32 are not supported on those platform currently.
I'm working on a solution to this PR, particularly how to ensure successful compilation when multiple arch build.

[yingluAMD]

Convert to draft PR because it is under development now.

[yingluAMD]

Update this PR, remove gfx from CPU code is not final solution which introduces build fail on un-support TF32 platform.
Add CK_ENABLE_TF32 to control whether enroll this datatypes compilation. Validated on gfx90a, gfx942 and gfx950.

[bartekxk]

LGTM, minor comment