AI/rocm-systems
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix spelling errors

Browse Source 
Conflicts:
	README.md
	docs/markdown/hip_faq.md

Change-Id: I8ca025e01276939ed3d7be24200ecaa8cf5e1e2c


[ROCm/hip commit: 65ad9d80d7]
This commit is contained in:
Robert
2016-12-19 17:36:07 -08:00
committed by Maneesh Gupta
parent d30f6a1d1b
commit a0cb435ab9
7 changed files with 41 additions and 41 deletions
Download Patch File Download Diff File Expand all files Collapse all files
projects/hip/CONTRIBUTING.md
+1 -1
View File
@@ -126,7 +126,7 @@ Differences or limitations of HIP APIs as compared to CUDA APIs should be clearl
- All HIP environment variables should begin with the keyword HIP_
Environment variables should be long enough to describe their purpose but short enough so they can be remembered - perhaps 10-20 characters, with 3-4 parts separated by underscores.
To see the list of current environment variables, along with their values, set HIP_PRINT_ENV and run any hip applications on ROCM platform .
To see the list of current environment variables, along with their values, set HIP_PRINT_ENV and run any hip applications on ROCm platform .
HIPCC or other tools may support additional environment variables which should follow the above convention.