Go compiler hardens binaries, crypto tightens SSH safety

The month's most consequential work landed in the compiler, where stack object records now use pointer-size alignment [1] and mips64le pointer offsets beyond 32 bits are corrected [2]. These fixes shrink binaries on AMD64 and eliminate subtle miscompilations on MIPS64, changes that matter for anyone shipping to exotic architectures or watching binary size creep.

A second compiler thread tightened correctness around range-clear safety [3] and load merging, which now tracks visited values instead of iterations to avoid missing merge opportunities [4]. The inliner's disjointness check also shifted to use types recorded in Store operations [5], improving optimization precision. Meanwhile, internal SSA refactoring added an HTML debug flag [6] and removed the HTMLWriter from Func [7], laying groundwork for future debug tooling.

The crypto and net stack saw targeted fixes. The SSH implementation now returns window credit for discarded extended data [8], preventing stalls in channels. Poly1305 gained optimized assembly for riscv64 [9], and so does x86 ABI0 NOFRAME BP expectations [10]—a breaking fix for code relying on the prior behavior. A fixed frame pointer adjustment around injected calls [11] closes a subtle runtime bug.

On the tooling side, vscode-go updated impl to v1.5.0 [12]. The pkgsite frontend improved documentation signals by checking local interfaces [13] and accepting group comments [14], making generated docs more accurate. Benchmarks shifted from benchmarks-50 to benchmarks-100 [15], which should give larger, more stable sample sets for regression detection.

Cleanups continued steadily: net/rpc dropped unused sort.Interface methods [16], and bytes/strings removed redundant DecodeRune fast paths [17]. The latter is a small but real simplification of hot-path code.