You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We do not export macro as a part of our public API and therefore it is OK to define whatever we want.
If CK exports its own macro (ENV) in its public API, then it is CK who must take care about possible collisions with their users, for example by adding and unique prefix (like CK_ or COMPOSABLE_KERNELS_). Or, better, they should avoid exporting macros in their API.
Thanks for fixing the problem.
We do not export macro as a part of our public API and therefore it is OK to define whatever we want.
If CK exports its own macro (
ENV
) in its public API, then it is CK who must take care about possible collisions with their users, for example by adding and unique prefix (likeCK_
orCOMPOSABLE_KERNELS_
). Or, better, they should avoid exporting macros in their API.I'll take care about this.
Originally posted by @atamazov in ROCm/MIOpen#2961 (comment)
The text was updated successfully, but these errors were encountered: