HIPCONFIG(1)

πŸ“¦
version 10.0 Β· 2 versions
, in ubuntu resolute, ubuntu stonking

πŸ’– HIPCONFIG(1) β€” hipconfig πŸ’–

okay bestie, sit down, we're doing the HIP configuration information utility, and honestly? it's giving ✨*utility*✨ in the best way. manual section 1, user commands, the whole vibe.


🌸 NAME 🌸

hipconfig β€” the HIP configuration information utility. that's it. that's the girl. she answers questions about your HIP setup and she does NOT gatekeep. 🫢


✨ SYNOPSIS ✨

usage: hipconfig [OPTIONS]

that's the whole thing. no arguments, no drama, just options. periodt. πŸ’…


πŸŽ€ DESCRIPTION πŸŽ€

so the hipconfig utility is your little bestie for querying information about your HIP installation. you wanna know the version? the installation path? which compiler? which target platform? she knows. she always knows. πŸ’β€β™€οΈ

ngl it's literally the "hey girl what's going on with my HIP install" tool and we're obsessed. 🌸


πŸ¦‹ OPTIONS πŸ¦‹

every single one of these matters, so here they all are, no skipping, no "oh you'll figure it out":

  • --path, -p β€” prints HIP_PATH. if the env var is set, she uses it; otherwise she figures it out from the hipconfig path. resourceful queen. πŸ‘‘
  • --rocmpath, -R β€” prints ROCM_PATH. env var set? use it. not set? she determines it from the hip path or falls back to /opt/rocm. she's got options, lowkey. πŸ’œ
  • --cpp_config, -C β€” prints the C++ compiler options. the receipts, basically. 🧾
  • --compiler, -c β€” prints the compiler. that's clang or nvcc, bestie. pick your fighter. βš”οΈ
  • --platform, -P β€” prints the platform. amd or nvidia. the eternal question. 🌈
  • --runtime, -r β€” prints the runtime. rocclr or cuda. the sequel nobody asked for but we love anyway. πŸ”₯
  • --hipclangpath, -l β€” prints HIP_CLANG_PATH. say that five times fast, i dare you. 😭
  • --full, -f β€” prints the full config. the whole meal. the entire buffet. no crumbs left. πŸ“
  • --version, -v β€” prints the hip version. useful for bug reports and for flexing. πŸ’…
  • --check β€” checks the configuration. like a vibe check but for your install. ⭐
  • --newline, -n β€” prints a newline. that's it. that's the job. tiny but mighty. πŸŽ€
  • --help, -h β€” prints the help message. when in doubt, ask for help, and that's on self-care. 🫢

🌈 ENVIRONMENT 🌈

here's where the plot thickens β€” all the env vars that shape what hipconfig tells you:

πŸ’œ HIP_PLATFORM

the $HIP_PLATFORM variable is used to explicitly specify the target platform for hipcc. valid options are "amd" and "nvidia". πŸ‘‘

πŸ’œ HIP_COMPILER

the $HIP_COMPILER variable specifies the target compiler for hipcc. valid options are "clang" and "nvcc". and btw? this one is usually set automatically based on whatever $HIP_PLATFORM is doing. she's a follower, but in a cute way. πŸ¦‹

πŸ’œ HIP_RUNTIME

the $HIP_RUNTIME variable specifies the target runtime for hipcc. valid options are "rocclr" and "cuda". same deal β€” this variable is usually set automatically based on the value of $HIP_PLATFORM. ✨

πŸ’œ ROCM_PATH

the $ROCM_PATH variable specifies the path to the AMD ROCm tools and libraries. this one defaults to "/usr". noted. πŸ“Œ

πŸ’œ CUDA_PATH

the $CUDA_PATH variable specifies the path to the CUDA tools and libraries. this one defaults to "/usr/local/cuda". iconic path, no notes. 🌸

πŸ’œ HIP_PATH

the $HIP_PATH variable specifies the path to the base directory of the HIP runtime library. and here's the caveat bestie β€” this variable is not typically used when building on Debian. so if you're on Debian, don't come for her. πŸ’€

πŸ’œ HIP_ROCCLR_HOME

the $HIP_ROCCLR_HOME variable specifies the path to the base directory of the HIP runtime library. same energy as above: not typically used when building on Debian. 🫢

πŸ’œ HIP_CLANG_PATH

the $HIP_CLANG_PATH variable specifies the path to the base directory of the HIP clang compiler. and yeah, you guessed it β€” not typically used when building on Debian. the Debian girlies are just built different, iykyk. 😭


πŸ’– reminder: env vars are the main characters here, they're literally deciding what gets printed. so if something looks weird, check your environment first, bestie. not me learning that the hard way πŸ’€

and that's the whole page, no cap. this was hipconfig version 7.0.1, dated October 2025, living in manual section 1. mwah, go configure something gorgeous. πŸ’…βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from