Go: Portable SIMD Push, MIPS Sleep Fix and Faster Maps

The dominant pattern is steady work to make the portable SIMD vector API complete across all hardware targets, alongside tooling cleanup. The highest-impact fixes are a microsecond sleep bug on MIPS that burned CPU and a maps copy optimization cutting time in half.

Duration: PT2M12S

Episode overview

This episode is a short developer briefing from Go.

It explains recent repository work in plain language.

  • Show: Go
  • Published: 2026-11-07T14:05:37Z
  • Audio duration: PT2M12S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good morning, it's November 7th, 2026, and this is your Go briefing.

The lead today is convergence: a cluster of vector instruction work aimed at a truly portable SIMD API, paired with two high-impact reliability and performance fixes you will feel directly.

First, portable vectors. A pair of changes adds a high-to-low move operation on every target and adds interleave and concat operations on ARM scalable vectors, built from existing primitives on AMD 64, ARM 64 and WebAssembly. That fills a gap for upcoming narrowing and widening conversions, where only the low half…

Second, performance and correctness in the runtime. PR 82914 fixes the microsecond sleep helper on Linux MIPS systems. The remainder was passed to the system unscaled, so a request for milliseconds slept for nanoseconds. On an idle router, the system monitor woke about ten thousand times per second and used a…

Third, compiler and tooling polish. Two RISC-V compiler changes use single-bit set and flip instructions but limit them to the newer profile, because widely available hardware lacks the extension. And PR 82912 makes the documentation tool reject a version qualifier for standard library packages instead of…

What's…

Nearby episodes from Go

  1. Secure Cookies and Portable Vector Support
  2. Simd Generator Speedups, Faster Headers and Clearer Docs
  3. Weekly Recap - Math Precision, Network Edge Cases, and Toolchain Polish
  4. Math Precision and Coverage Reliability
  5. Math Precision Fixes and Runtime Stability
  6. Compiler Correctness and HTTP Server Consistency
  7. HTTP Hardening, Stack Reuse, and Apple Silicon Security
  8. HTTP Spec Corrections and Toolchain Stability