# CMAKE\_HIP\_KNOWN\_FEATURES

**URL:** <https://discourse.cmake.org/t/cmake-hip-known-features/10907>\
**Category:** Code\
**Created:** [May 24, 2024, 8:28pm UTC](https://discourse.cmake.org/t/cmake-hip-known-features/10907 "2024-05-24T20:28:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![elliottslaughter](https://discourse.cmake.org/user_avatar/discourse.cmake.org/elliottslaughter/32/4609_2.png) [@elliottslaughter](https://discourse.cmake.org/u/elliottslaughter)\
**Post date:** [May 24, 2024, 8:28pm UTC](https://discourse.cmake.org/t/cmake-hip-known-features/10907/1 "2024-05-24T20:28:28Z")

</div>

Apparently, we have:

[https://cmake.org/cmake/help/latest/prop\_gbl/CMAKE\_CXX\_KNOWN\_FEATURES.html](https://cmake.org/cmake/help/latest/prop_gbl/CMAKE_CXX_KNOWN_FEATURES.html)

and

[https://cmake.org/cmake/help/latest/prop\_gbl/CMAKE\_CUDA\_KNOWN\_FEATURES.html](https://cmake.org/cmake/help/latest/prop_gbl/CMAKE_CUDA_KNOWN_FEATURES.html)

but there is no equivalent for HIP.

Is this an oversight? It seems unfortunate to have HIP be a language in CMake but not actually have that support be full-featured, as C++ standards are something that HIP users need just as much as CUDA.

Thanks.

---

<div class="post-metadata">

**Author:** ![ben.boeckel](https://discourse.cmake.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.cmake.org/u/ben.boeckel)\
**Post date:** [March 13, 2025, 6:21pm UTC](https://discourse.cmake.org/t/cmake-hip-known-features/10907/2 "2025-03-13T18:21:43Z")

</div>

Seems like an oversight to me.

Thoughts? @brad.king @zackgalbreath

---

<div class="post-metadata">

**Author:** ![brad.king](https://discourse.cmake.org/user_avatar/discourse.cmake.org/brad.king/32/11_2.png) [@brad.king](https://discourse.cmake.org/u/brad.king)\
**Post date:** [March 13, 2025, 6:48pm UTC](https://discourse.cmake.org/t/cmake-hip-known-features/10907/3 "2025-03-13T18:48:15Z")

</div>

This was also reported as [CMake Issue 26013](https://gitlab.kitware.com/cmake/cmake/-/issues/26013), and is fixed as of CMake 3.30.