Skip to content

Commit 18e0a83

Browse files
randyh62neon60
authored andcommitted
Update docs/how-to/hip_porting_guide.rst
1 parent 5b8e987 commit 18e0a83

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

docs/how-to/hip_porting_guide.rst

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -196,7 +196,7 @@ Library equivalents
196196

197197
ROCm provides libraries to ease porting of code relying on CUDA libraries.
198198
Most CUDA libraries have a corresponding HIP library. For more information,
199-
see :ref:`<hipify:reference/supported_apis>`, or :ref:`<rocm:reference/api-libraries>`.
199+
see either :doc:`ROCm libraries <rocm:reference/api-libraries>` or :doc:`HIPIFY CUDA compatible libraries <hipify:reference/supported_apis>`.
200200

201201
There are two flavours of libraries provided by ROCm, ones prefixed with ``hip``
202202
and ones prefixed with ``roc``. While both are written using HIP, in general
@@ -261,6 +261,7 @@ platform:
261261
- ``.fatbin``
262262
- ``.hip_fatbin``
263263

264+
264265
``hipcc`` uses HIP-Clang or NVCC to compile host code. Both of these compilers can
265266
embed code objects into the final executable. These code objects are automatically
266267
loaded when the application starts. The ``hipModule`` API can be used to load

0 commit comments

Comments
 (0)