qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-23 12:30:11 -07:00
Code Releases Activity

doc/go1.18: move fuzzing to tools section

Browse Source 
For #47694

Change-Id: Idab1a5822a096447c71776ee4339c4262183ceb7
Reviewed-on: https://go-review.googlesource.com/c/go/+/370034
Trust: Ian Lance Taylor <iant@golang.org>
Run-TryBot: Ian Lance Taylor <iant@golang.org>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Katie Hockman <katie@golang.org>
Trust: Katie Hockman <katie@golang.org>
This commit is contained in:
Ian Lance Taylor 2021-12-07 09:50:44 -08:00
parent 016e6ebb42
commit a19e72cb89
1 changed files with 21 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
doc/go1.18.html
View File

@ -112,27 +112,6 @@ Do not send CLs removing the interior tags from such phrases.
programs is likely very small.
</p>
<h3 id="fuzzing">Fuzzing</h3>
<p>
Go 1.18 includes an implementation of fuzzing as described by
<a href="https://golang.org/issue/44551">the fuzzing proposal</a>.
</p>
<p>
See the <a href="https://go.dev/doc/fuzz">fuzzing landing page</a> to get
started.
</p>
<p>
Please be aware that fuzzing can consume a lot of memory and may impact your
machine’s performance while it runs. Also be aware that the fuzzing engine
writes values that expand test coverage to a fuzz cache directory within
<code>$GOCACHE/fuzz</code> while it runs. There is currently no limit to the
number of files or total bytes that may be written to the fuzz cache, so it
may occupy a large amount of storage (possibly several GBs).
</p>
<h2 id="ports">Ports</h2>
<h3 id="amd64">AMD64</h3>
@ -183,6 +162,27 @@ Do not send CLs removing the interior tags from such phrases.
<h2 id="tools">Tools</h2>
<h3 id="fuzzing">Fuzzing</h3>
<p>
Go 1.18 includes an implementation of fuzzing as described by
<a href="https://golang.org/issue/44551">the fuzzing proposal</a>.
</p>
<p>
See the <a href="https://go.dev/doc/fuzz">fuzzing landing page</a> to get
started.
</p>
<p>
Please be aware that fuzzing can consume a lot of memory and may impact your
machine’s performance while it runs. Also be aware that the fuzzing engine
writes values that expand test coverage to a fuzz cache directory within
<code>$GOCACHE/fuzz</code> while it runs. There is currently no limit to the
number of files or total bytes that may be written to the fuzz cache, so it
may occupy a large amount of storage (possibly several GBs).
</p>
<h3 id="go-command">Go command</h3>
<p><!-- golang.org/issue/43684 -->