From d6c5a2539f091c564dd38e9be81a3475bb01e651 Mon Sep 17 00:00:00 2001 From: Tomas Wood Date: Sat, 9 Jun 2018 17:16:08 -0700 Subject: [PATCH] Update hip_porting_guide.md use ".hip.cpp" for *source* files [ROCm/hip commit: ed7dee4d197bd0a00982890e33054922de57f50c] --- projects/hip/docs/markdown/hip_porting_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/projects/hip/docs/markdown/hip_porting_guide.md b/projects/hip/docs/markdown/hip_porting_guide.md index aeb7b171d6..9810918174 100644 --- a/projects/hip/docs/markdown/hip_porting_guide.md +++ b/projects/hip/docs/markdown/hip_porting_guide.md @@ -393,7 +393,7 @@ The hcc path provides an empty cuda.h file. Some existing Cuda programs include Many existing Cuda projects use the ".cu" and ".cuh" file extensions to indicate code that should be run through the nvcc compiler. For quick HIP ports, leaving these file extensions unchanged is often easier, as it minimizes the work required to change file names in the directory and #include statements in the files. -For new projects or ports which can be re-factored, we recommend the use of the extension ".hip.cpp" for header files, and +For new projects or ports which can be re-factored, we recommend the use of the extension ".hip.cpp" for source files, and ".hip.h" or ".hip.hpp" for header files. This indicates that the code is standard C++ code, but also provides a unique indication for make tools to run hipcc when appropriate.