qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-14 22:40:40 -07:00
Code Releases Activity

cmd/cgo: update outdated docs about cgocheck2

Browse Source 
Setting GODEBUG=cgocheck=2 now panics with a message
such as "fatal error: cgocheck > 1 mode is no longer supported at runtime.
Use GOEXPERIMENT=cgocheck2 at build time instead."

Change-Id: If9a5a96933973e14a1a60b8e9fb6a1f4a818cf59
GitHub-Last-Rev: 787d62454c
GitHub-Pull-Request: golang/go#65224
Reviewed-on: https://go-review.googlesource.com/c/go/+/557597
Reviewed-by: Ian Lance Taylor <iant@google.com>
Reviewed-by: qiulaidongfeng <2645477756@qq.com>
Reviewed-by: Keith Randall <khr@google.com>
Reviewed-by: Keith Randall <khr@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
This commit is contained in:
Kévin Dunglas 2024-03-30 09:13:39 +00:00 committed by Emmanuel Odeke
parent ba9c445f16
commit d49a14c609
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
src/cmd/cgo/doc.go
View File

@ -402,7 +402,8 @@ controlled by the cgocheck setting of the GODEBUG environment
variable. The default setting is GODEBUG=cgocheck=1, which implements
reasonably cheap dynamic checks. These checks may be disabled
entirely using GODEBUG=cgocheck=0. Complete checking of pointer
handling, at some cost in run time, is available via GODEBUG=cgocheck=2.
handling, at some cost in run time, is available by setting
GOEXPERIMENT=cgocheck2 at build time.
It is possible to defeat this enforcement by using the unsafe package,
and of course there is nothing stopping the C code from doing anything