From e8f4f7664915e12cfec8d5ebf61c1df7cd50afe3 Mon Sep 17 00:00:00 2001
From: Ben Sander <ben.sander@amd.com>
Date: Wed, 5 Apr 2017 21:59:11 -0500
Subject: [PATCH] Update bug workarounds to reflect tool improvements.

---
 hipamd/docs/markdown/hip_bugs.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/hipamd/docs/markdown/hip_bugs.md b/hipamd/docs/markdown/hip_bugs.md
index c53b68d796..14f2935f17 100644
--- a/hipamd/docs/markdown/hip_bugs.md
+++ b/hipamd/docs/markdown/hip_bugs.md
@@ -9,23 +9,23 @@
 
 <!-- tocstop -->
 
-### Errors related to undefined reference to `__hcLaunchKernel__***__grid_launch_parm**
+### Errors related to undefined reference to `__hcLaunchKernel__***__grid_launch_parm**`
 
 Some common code practices may lead to hipcc generating a error with the form :
 undefined reference to `__hcLaunchKernel__ZN15vecAddNamespace6vecAddIidEEv16grid_launch_parmPT0_S3_S3_T_
 
-To workaround, try:
-- Avoid calling hipLaunchKernel from a function with the __host__ attribute
-```
-__host__ MyFunc(…) {
-hipLaunchKernel(myKernel, …)
-```
+Suggested workarounds:
 - Avoid use of static with kernel definition:
+```c++
 static __global__ MyKernel 
-- Avoid defining kernels in anonymous namespace
+```
+
+- Avoid defining kernels in anonymous namespace :
+```c++
 namespace {
-__global__ MyKernel …
-- Avoid calling member functions 
+  __global__ MyKernel
+}
+```
 
 
 ### What is the current limitation of HIP Generic Grid Launch method?