Ian Lance Taylor d91ec5bb40 cmd/cgo, runtime: recognize unsafe.Pointer(&s[0]) in cgo pointer checks ... It's fairly common to call cgo functions with conversions to unsafe.Pointer or other C types. Apply the simpler checking of address expressions when possible when the address expression occurs within a type conversion. Change-Id: I5187d4eb4d27a6542621c396cad9ee4b8647d1cd Reviewed-on: https://go-review.googlesource.com/18391 Run-TryBot: Ian Lance Taylor <iant@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Russ Cox <rsc@golang.org>		2016-01-08 03:56:30 +00:00
..
err1.go
err2.go
err3.go
issue7757.go
issue8442.go
issue11097a.go	cmd/cgo: fix panic on references to non-existing C types	2015-10-05 22:37:07 +00:00
issue11097b.go	cmd/cgo: fix panic on references to non-existing C types	2015-10-05 22:37:07 +00:00
issue13129.go	cmd/cgo: handle another Clang DWARF quirk	2015-11-25 21:13:41 +00:00
issue13423.go	cmd/cgo: error, not panic, if not enough arguments to function	2015-12-02 21:02:28 +00:00
issue13635.go	cmd/cgo: map C unsigned char back to _Ctype_uchar in error messages	2015-12-16 22:13:17 +00:00
ptr.go	cmd/cgo, runtime: recognize unsafe.Pointer(&s[0]) in cgo pointer checks	2016-01-08 03:56:30 +00:00
test.bash	cmd/cgo: map C unsigned char back to _Ctype_uchar in error messages	2015-12-16 22:13:17 +00:00