An error occurred fetching the project authors.
  1. 22 Aug, 2016 1 commit
  2. 24 Dec, 2015 1 commit
    • Ian Lance Taylor's avatar
      runtime: adjust gsignal stack to current signal stack · f7e51c13
      Ian Lance Taylor authored
      If non-Go code calls sigaltstack before a signal is received, use
      sigaltstack to determine the current signal stack and set the gsignal
      stack to use it.  This makes the Go runtime more robust in the face of
      non-Go code.  We still can't handle a disabled signal stack or a signal
      triggered with SA_ONSTACK clear, but we now give clear errors for those
      cases.
      
      Fixes #7227.
      Update #9896.
      
      Change-Id: Icb1607e01fd6461019b6d77d940e59b3aed4d258
      Reviewed-on: https://go-review.googlesource.com/18102
      Run-TryBot: Ian Lance Taylor <iant@golang.org>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: default avatarMikio Hara <mikioh.mikioh@gmail.com>
      f7e51c13
  3. 10 Nov, 2015 1 commit
    • Michael Matloob's avatar
      runtime: break atomics out into package runtime/internal/atomic · 67faca7d
      Michael Matloob authored
      This change breaks out most of the atomics functions in the runtime
      into package runtime/internal/atomic. It adds some basic support
      in the toolchain for runtime packages, and also modifies linux/arm
      atomics to remove the dependency on the runtime's mutex. The mutexes
      have been replaced with spinlocks.
      
      all trybots are happy!
      In addition to the trybots, I've tested on the darwin/arm64 builder,
      on the darwin/arm builder, and on a ppc64le machine.
      
      Change-Id: I6698c8e3cf3834f55ce5824059f44d00dc8e3c2f
      Reviewed-on: https://go-review.googlesource.com/14204
      Run-TryBot: Michael Matloob <matloob@golang.org>
      Reviewed-by: default avatarRuss Cox <rsc@golang.org>
      67faca7d
  4. 30 Jul, 2015 1 commit
  5. 27 Jul, 2015 1 commit
  6. 19 Jun, 2015 1 commit
    • Austin Clements's avatar
      runtime: ensure GC sees type-safe memory on weak machines · f5d494bb
      Austin Clements authored
      Currently its possible for the garbage collector to observe
      uninitialized memory or stale heap bitmap bits on weakly ordered
      architectures such as ARM and PPC. On such architectures, the stores
      that zero newly allocated memory and initialize its heap bitmap may
      move after a store in user code that makes the allocated object
      observable by the garbage collector.
      
      To fix this, add a "publication barrier" (also known as an "export
      barrier") before returning from mallocgc. This is a store/store
      barrier that ensures any write done by user code that makes the
      returned object observable to the garbage collector will be ordered
      after the initialization performed by mallocgc. No barrier is
      necessary on the reading side because of the data dependency between
      loading the pointer and loading the contents of the object.
      
      Fixes one of the issues raised in #9984.
      
      Change-Id: Ia3d96ad9c5fc7f4d342f5e05ec0ceae700cd17c8
      Reviewed-on: https://go-review.googlesource.com/11083Reviewed-by: default avatarRick Hudson <rlh@golang.org>
      Reviewed-by: default avatarDmitry Vyukov <dvyukov@google.com>
      Reviewed-by: default avatarMinux Ma <minux@golang.org>
      Reviewed-by: default avatarMartin Capitanio <capnm9@gmail.com>
      Reviewed-by: default avatarRuss Cox <rsc@golang.org>
      f5d494bb
  7. 14 Apr, 2015 1 commit
  8. 21 Mar, 2015 1 commit
  9. 15 Mar, 2015 1 commit