$ the-wire · showcase
darwin/amd64 goes always-PIE, and archsimd settles its naming
By RepoJournal · Filed · About Go · Composed from the cited sources · methodology
The Go tree spent the day tightening darwin linking and cleaning up experimental SIMD and cgo surfaces, while x/tools fixed an analysistest check that misfired on every caller and gopls corrected a telemetry-reported package matching bug.
cmd/link: make darwin/amd64 always PIE golang/go
cmd/link now uses BuildModePIE for -buildmode=exe on darwin/amd64, matching darwin/arm64. The toolchain's own notes point at the cause: runtime/cgo and //cgo:binding emit R_ADDR relocations in __DATA targeting SDYNIMPORT symbols, "which require LC_DYLD_INFO_ONLY (only emitted by cmd/link in PIE mode)," and Apple's linker has deprecated -no_pie.
simd/archsimd: rename ConcatShiftBytesRight to ConcatWindow golang/go
ConcatShiftBytesRight and ConcatShiftBytesRightGrouped become ConcatWindow and ConcatWindowGrouped, with the receiver and vector argument swapped and the index narrowed to uint8. The old methods stay as deprecated wrappers that go fix can inline, so existing archsimd callers compile but will need the rewrite before the wrappers go.
simd/archsimd: rename AES and carryless multiply CPU feature queries golang/go
The X86Features AES and carryless-multiply queries are renamed off a mix of Intel CPUID names (VAES, VPCLMULQDQ), XED ISA set names (AVXAES, AVX512VAES, AVX512VPCLMULQDQ) and the invented AVXPCLMULQDQ so the three vector widths relate to each other by name. archsimd is still experimental, so the rename costs nothing outside code already written against it.
go/analysis/analysistest: fix check for callers in x/tools golang/tools
RunWithSuggestedFixes required a Diagnostic.Category for fixes without TextEdits only when the caller was in x/tools, but runtime.Callers(1, ...) returned RunWithSuggestedFixes itself, so the check applied to every caller. Analyzers enforcing that rule were failing outside x/tools with the gopls "missing Diagnostic.Category" error.
cmd/go, runtime/cgo: remove gcc_util.c on Go-cgo targets golang/go
gcc_util.c is excluded on GOEXPERIMENT=cgobindings targets: _cgo_yield moves to callbacks_c.go, the C TSAN/MSAN cgo_import_static declarations come out of cgo.go, and the runtime/cgo sanitizer hooks become no-ops, with -msan and C TSAN/MSAN tests disabled until Go-side sanitizer registration lands. The rest is quiet: dependency bumps across x/tools, pkgsite-metrics, vuln and build
gopls/internal/cache/metadata: take care in IsCommandLineArguments golang/tools
gopls's IsCommandLineArguments used strings.Contains, so it matched intermediate test variants like "tool [command-line-arguments.test]" and real packages whose import path contains the string. A telemetry report caught it; the match is now exact.