Skip to content

Commit bdb8daa

Browse files
randyh62jujiang-del
authored andcommitted
Update docs/how-to/hip_porting_guide.rst
Co-authored-by: Julia Jiang <56359287+jujiang-del@users.noreply.github.com>
1 parent e7049c6 commit bdb8daa

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/how-to/hip_porting_guide.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
.. meta::
2-
:description: This chapter presents how to port the CUDA API to HIP API
2+
:description: This chapter presents how to port the CUDA source code to HIP
33
:keywords: AMD, ROCm, HIP, CUDA, driver API, porting, port
44

55
.. _porting_cuda_code:
@@ -13,7 +13,7 @@ environment, enabling you to run your application on AMD GPUs. This topic descri
1313
the available tools and provides practical suggestions for porting your CUDA
1414
code and working through common issues.
1515

16-
CUDA provides separate driver and runtime APIs, while HIP uses a single API.
16+
CUDA provides separate driver and runtime APIs, while HIP mostly uses a single API.
1717
The two CUDA APIs generally provide similar functionality and are mostly interchangeable.
1818
However, the CUDA driver API provides fine-grained control over kernel-level
1919
initialization, contexts, and module management, while the runtime API automatically

0 commit comments

Comments
 (0)