Skip to content

Commit 5b8e987

Browse files
randyh62neon60
authored andcommitted
Update hip_porting_guide.rst
indent HIPIFY bullets
1 parent e04fa28 commit 5b8e987

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/how-to/hip_porting_guide.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -81,14 +81,14 @@ HIP unifies the APIs for these common functions.
8181
There are two types of HIPIFY available:
8282

8383
* :doc:`hipify-clang <hipify:how-to/hipify-clang>` is a Clang-based tool that parses code,
84-
translates it into an Abstract Syntax Tree, and generates the HIP source. For this,
85-
``hipify-clang`` needs to be able to actually compile the code, so the CUDA code needs
86-
to be correct, and a CUDA install with all necessary headers must be provided.
84+
translates it into an Abstract Syntax Tree, and generates the HIP source. For this,
85+
``hipify-clang`` needs to be able to actually compile the code, so the CUDA code needs
86+
to be correct, and a CUDA install with all necessary headers must be provided.
8787

8888
* :doc:`hipify-perl <hipify:how-to/hipify-perl>` uses pattern matching, to translate the
89-
CUDA code to HIP. It does not require a working CUDA installation, and can also
90-
convert CUDA code, that is not syntactically correct. It is therefore easier to
91-
set up and use, but is not as powerful as ``hipfiy-clang``.
89+
CUDA code to HIP. It does not require a working CUDA installation, and can also
90+
convert CUDA code, that is not syntactically correct. It is therefore easier to
91+
set up and use, but is not as powerful as ``hipfiy-clang``.
9292

9393
Memory copy functions
9494
---------------------

0 commit comments

Comments
 (0)