From 537102af0a0959e660789dbe0aab02404eec0af2 Mon Sep 17 00:00:00 2001 From: "Yaxun (Sam) Liu" Date: Thu, 31 Jan 2019 16:26:30 -0500 Subject: [PATCH] Update hip_programming_guide.md --- hipamd/docs/markdown/hip_programming_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hipamd/docs/markdown/hip_programming_guide.md b/hipamd/docs/markdown/hip_programming_guide.md index b9ab362159..8922a7c4b3 100644 --- a/hipamd/docs/markdown/hip_programming_guide.md +++ b/hipamd/docs/markdown/hip_programming_guide.md @@ -113,4 +113,4 @@ allocated. ## Use of Long Double Type -In HCC and HIP-Clang, long double type is 80-bit extended precision format for x86_64, which is not supported by AMDGPU. HCC and HIP-Cang treat long double type as IEEE double type for AMDGPU. Using long double type in HIP source code will not cause issue as long as data of long double type is not transferred between host and device. However, long double type should not be used as kernel argument type. +In HCC and HIP-Clang, long double type is 80-bit extended precision format for x86_64, which is not supported by AMDGPU. HCC and HIP-Clang treat long double type as IEEE double type for AMDGPU. Using long double type in HIP source code will not cause issue as long as data of long double type is not transferred between host and device. However, long double type should not be used as kernel argument type.