Ian Lance Taylor 880a689124 runtime: don't call msanread when running on the system stack ... The runtime is not instrumented, but the calls to msanread in the runtime can sometimes refer to the system stack. An example is the call to copy in stkbucket in mprof.go. Depending on what C code has done, the system stack may appear uninitialized to msan. Change-Id: Ic21705b9ac504ae5cf7601a59189302f072e7db1 Reviewed-on: https://go-review.googlesource.com/16660 Reviewed-by: David Crawshaw <crawshaw@golang.org>		2015-11-11 06:04:04 +00:00
..
msan2.go	runtime: don't call msanread when running on the system stack	2015-11-11 06:04:04 +00:00
msan3.go	runtime: mark cgo callback results as written for msan	2015-11-11 05:58:19 +00:00
msan4.go	runtime: don't call msanread when running on the system stack	2015-11-11 06:04:04 +00:00
msan_fail.go	runtime: don't call msanread when running on the system stack	2015-11-11 06:04:04 +00:00
msan.go	runtime: don't call msanread when running on the system stack	2015-11-11 06:04:04 +00:00
test.bash	runtime: don't call msanread when running on the system stack	2015-11-11 06:04:04 +00:00