SWDEV-398297 - HIP Documentation Updates for ROCm 5.6-needed for 23.10 (#3250)
Change-Id: I514a0a941fcc6ebd940f5c6c6700c3c305f04a56
This commit is contained in:
committed by
GitHub
parent
22e9263088
commit
77831c91d8
@@ -7,7 +7,7 @@ Key features include:
|
||||
* HIP is very thin and has little or no performance impact over coding directly in CUDA mode.
|
||||
* HIP allows coding in a single-source C++ programming language including features such as templates, C++11 lambdas, classes, namespaces, and more.
|
||||
* HIP allows developers to use the "best" development environment and tools on each target platform.
|
||||
* The [HIPIFY](https://github.com/ROCm-Developer-Tools/HIPIFY/blob/master/README.md) tools automatically convert source from CUDA to HIP.
|
||||
* The [HIPIFY](https://github.com/ROCm-Developer-Tools/HIPIFY/blob/amd-staging/README.md) tools automatically convert source from CUDA to HIP.
|
||||
* Developers can specialize for the platform (CUDA or AMD) to tune for performance or handle tricky cases.
|
||||
|
||||
New projects can be developed directly in the portable HIP C++ language and can run on either NVIDIA or AMD platforms. Additionally, HIP provides porting tools which make it easy to port existing CUDA codes to the HIP layer, with no loss of performance as compared to the original CUDA application. HIP is not intended to be a drop-in replacement for CUDA, and developers should expect to do some manual coding and performance tuning work to complete the port.
|
||||
|
||||
Reference in New Issue
Block a user