From: Austin Clements Date: Fri, 14 Jun 2019 19:02:35 +0000 (-0400) Subject: doc/go1.13: runtime release notes, some compiler release notes X-Git-Tag: go1.13beta1~59 X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=bd7d1bb8f32b6da33b78804ae8d61e44a1c3f981;p=gostls13.git doc/go1.13: runtime release notes, some compiler release notes Change-Id: Icc5083a3de0c6b737bfc20b573ed785651910148 Reviewed-on: https://go-review.googlesource.com/c/go/+/182461 Reviewed-by: Andrew Bonventre --- diff --git a/doc/go1.13.html b/doc/go1.13.html index 1f83c0d9a0..829542f4b2 100644 --- a/doc/go1.13.html +++ b/doc/go1.13.html @@ -44,12 +44,26 @@ TODO TODO

+

+ TODO: https://golang.org/cl/158797: implement shifts by signed amounts +

+

Ports

TODO

+

+ TODO: https://golang.org/cl/174457: add new GOOS=illumos, split out of GOOS=solaris +

+ +

Android

+ +

+ Go programs are now compatible with Android Q. +

+

Darwin

@@ -67,18 +81,64 @@ TODO FreeBSD 12.0 or later requires a kernel with the COMPAT_FREEBSD11 option set (this is the default).

+

AIX on PPC64

+ +

+ AIX on PPC64 now supports cgo and external linking. +

+

Tools

TODO

+

Compiler toolchain

+ +

+ The compiler has a new implementation of escape analysis that is + more precise. For most Go code should be an improvement (in other + words, more Go variables and expressions allocated on the stack + instead of heap). However, this increased precision may also break + invalid code that happened to work before (for example, code that + violates + the unsafe.Pointer + safety rules). If you notice any regressions that appear + related, the old escape analysis pass can be re-enabled + with go build -gcflags=all=-newescape=false. + The option to use the old escape analysis will be removed in a + future release. +

+ +

+ The compiler no longer emits floating point or complex constants + to go_asm.h files. These have always been emitted in a + form that could not be used as numeric constant in assembly code. +

+

Runtime

-

-TODO +

+ Out of range panic messages now include the index that was out of + bounds and the length (or capacity) of the slice. For + example, s[3] on a slice of length 1 will panic with + "runtime error: index out of range [3] with length 1".

+

+ This release improves performance of most uses of defer + by 30%. +

+ +

+ The runtime is now more aggressive at returning memory to the + operating system to make it available to co-tenant applications. + Previously, the runtime could retain memory for five or more minutes + following a spike in the heap size. It will now begin returning it + promptly after the heap shrinks. However, on many OSes, including + Linux, the OS itself reclaims memory lazily, so process RSS will not + decrease until the system is under memory pressure. +

Core library

@@ -105,9 +165,6 @@ TODO; link to Go 1.12 notes. TODO

- - - @@ -115,14 +172,6 @@ TODO -
all
-
-

- TODO: https://golang.org/cl/174457: add new GOOS=illumos, split out of GOOS=solaris -

- -
-
bytes

@@ -175,7 +224,12 @@ TODO

debug/dwarf

- TODO: https://golang.org/cl/158797: more graceful handling of unsupported types + The Data.Type + method no longer panics if it encounters an unknown DWARF tag in + the type graph. Instead, it represents that component of the + type with + an UnsupportedType + object.

@@ -312,22 +366,6 @@ TODO
-
runtime, internal/poll, net
-
-

- TODO: https://golang.org/cl/166497: report event scanning error on read event -

- -
- -
runtime/cgo
-
-

- TODO: https://golang.org/cl/170127: look for android_get_device_api_level in libc.so -

- -
-
strings