mirror of
https://github.com/golang/go
synced 2024-11-26 23:01:23 -07:00
doc/go1.14: -d=checkptr is not yet recommended on Windows
Hopefully we'll have the remaining safety violations in the standard library ironed out by 1.15. We also fix a minor (but important) typo while we're here. Updates #34964, #34972. Change-Id: Ic72fd4d9411b749f8c0cea87e95ab68347009893 Reviewed-on: https://go-review.googlesource.com/c/go/+/214118 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
This commit is contained in:
parent
10bfe5b961
commit
199bc0003d
@ -301,9 +301,9 @@ TODO
|
|||||||
This release adds <code>-d=checkptr</code> as a compile-time option
|
This release adds <code>-d=checkptr</code> as a compile-time option
|
||||||
for adding instrumentation to check that Go code is following
|
for adding instrumentation to check that Go code is following
|
||||||
<code>unsafe.Pointer</code> safety rules dynamically.
|
<code>unsafe.Pointer</code> safety rules dynamically.
|
||||||
This option is enabled by default with the <code>-race</code>
|
This option is enabled by default (except on Windows) with
|
||||||
or <code>-msan</code> flags, and can be disabled
|
the <code>-race</code> or <code>-msan</code> flags, and can be
|
||||||
with <code>-gcflags=-all=-d=checkptr=0</code>.
|
disabled with <code>-gcflags=all=-d=checkptr=0</code>.
|
||||||
Specifically, <code>-d=checkptr</code> checks the following:
|
Specifically, <code>-d=checkptr</code> checks the following:
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
@ -320,6 +320,11 @@ TODO
|
|||||||
</li>
|
</li>
|
||||||
</ol>
|
</ol>
|
||||||
|
|
||||||
|
<p>
|
||||||
|
Using <code>-d=checkptr</code> is not currently recommended on
|
||||||
|
Windows because it causes false alerts in the standard library.
|
||||||
|
</p>
|
||||||
|
|
||||||
<p><!-- CL 204338 -->
|
<p><!-- CL 204338 -->
|
||||||
The compiler can now emit machine-readable logs of key optimizations
|
The compiler can now emit machine-readable logs of key optimizations
|
||||||
using the <code>-json</code> flag, including inlining, escape
|
using the <code>-json</code> flag, including inlining, escape
|
||||||
|
Loading…
Reference in New Issue
Block a user