From 179acf4083bedecad5f9700b86f6b58052b7526e Mon Sep 17 00:00:00 2001
From: Austin Clements
+ The compiler toolchain now uses different conventions to call Go + functions and assembly functions. This should be invisible to users, + except for calls that simultaneously cross between Go and + assembly and cross a package boundary. If linking results + in an error like "relocation target not defined for ABIInternal (but + is defined for ABI0)", please refer to help section of the ABI + design document. + TODO(austin): Link to the design doc. +
+ ++ There have been many improvements to the DWARF debug information + produced by the compiler, including improvements to argument + printing and variable location information. +
+@@ -211,6 +228,36 @@ for { for command-line help output instead.
++ The trace tool now supports plotting mutator utilization curves, + including cross-references to the execution trace. These are useful + for analyzing the impact of the garbage collector on application + latency and throughput. +
+ ++ Go 1.12 significantly improves the performance of sweeping when a + large fraction of the heap remains live. This reduces allocation + latency immediately following a garbage collection. +
+ ++ The Go runtime now releases memory back to the operating system more + aggressively, particularly in response to large allocations that + can't reuse existing heap space. +
+ ++ On Linux, the Go runtime now releases memory back to the operating + system only when the OS is under memory pressure. This is more + efficient, but means a process's RSS (resident set size) won't + decrease unless the OS is running out of memory. +
+@@ -231,7 +278,6 @@ for { -
- On Linux, the Go runtime now releases memory only when the OS is under memory - pressure. This is more efficient, but means a process's RSS (resident set size) - won't decrease unless the OS is running out of memory. -
- --- 2.50.0