Ian Lance Taylor 79ba1e44c7 cmd/cgo: mark stub functions as no_sanitize_thread ... When the generated stub functions write back the results to the stack, they can in some cases be writing to the same memory on the g0 stack. There is no race here (assuming there is no race in the Go code), but the thread sanitizer does not know that. Turn off the thread sanitizer for the stub functions to prevent false positive warnings. Current clang suggests the no_sanitize("thread") attribute, but that does not work with clang 3.6 or GCC. clang 3.6, GCC, and current clang all support the no_sanitize_thread attribute, so use that unconditionally. The test case and first version of the patch are from Dmitriy Vyukov. Change-Id: I80ce92824c6c8cf88ea0fe44f21cf50cf62474c9 Reviewed-on: https://go-review.googlesource.com/23252 Run-TryBot: Ian Lance Taylor <iant@golang.org> Reviewed-by: Dmitry Vyukov <dvyukov@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>		2016-05-19 17:29:13 +00:00
..
msan2.go	all: make copyright headers consistent with one space after period	2016-05-02 13:43:18 +00:00
msan3.go	cmd/cgo, runtime: exported Go functions can't return a Go pointer	2015-11-19 18:28:39 +00:00
msan4.go	all: make copyright headers consistent with one space after period	2016-05-02 13:43:18 +00:00
msan_fail.go	all: make copyright headers consistent with one space after period	2016-05-02 13:43:18 +00:00
msan.go	all: make copyright headers consistent with one space after period	2016-05-02 13:43:18 +00:00
test.bash	cmd/cgo: mark stub functions as no_sanitize_thread	2016-05-19 17:29:13 +00:00
tsan2.go	all: make copyright headers consistent with one space after period	2016-05-02 13:43:18 +00:00
tsan3.go	cmd/cgo: mark stub functions as no_sanitize_thread	2016-05-19 17:29:13 +00:00
tsan.go	all: make copyright headers consistent with one space after period	2016-05-02 13:43:18 +00:00