-
- Downloads
runtime: commit to spinbitmutex GOEXPERIMENT
Use the "spinbit" mutex implementation always (including on platforms that need to emulate atomic.Xchg8), and delete the prior "tristate" implementations. The exception is GOARCH=wasm, where the Go runtime does not use multiple threads. For #68578 Change-Id: Ifc29bbfa05071d776c23a19ae185891a03a82417 Reviewed-on: https://go-review.googlesource.com/c/go/+/658456 Auto-Submit: Rhys Hiltner <rhys.hiltner@gmail.com> Reviewed-by:Junyang Shao <shaojunyang@google.com> Reviewed-by:
Michael Knyszek <mknyszek@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Showing
- src/internal/buildcfg/exp.go 0 additions, 3 deletionssrc/internal/buildcfg/exp.go
- src/internal/goexperiment/exp_spinbitmutex_off.go 0 additions, 8 deletionssrc/internal/goexperiment/exp_spinbitmutex_off.go
- src/internal/goexperiment/exp_spinbitmutex_on.go 0 additions, 8 deletionssrc/internal/goexperiment/exp_spinbitmutex_on.go
- src/internal/goexperiment/flags.go 0 additions, 4 deletionssrc/internal/goexperiment/flags.go
- src/runtime/lock_futex_tristate.go 0 additions, 138 deletionssrc/runtime/lock_futex_tristate.go
- src/runtime/lock_sema_tristate.go 0 additions, 148 deletionssrc/runtime/lock_sema_tristate.go
- src/runtime/lock_spinbit.go 1 addition, 1 deletionsrc/runtime/lock_spinbit.go
- src/runtime/runtime2.go 3 additions, 4 deletionssrc/runtime/runtime2.go
Loading
Please register or sign in to comment