1. 11 Nov, 2015 4 commits
    • Ian Lance Taylor's avatar
      runtime: mark cgo callback results as written for msan · 8f3f2cca
      Ian Lance Taylor authored
      This is a fix for the -msan option when using cgo callbacks.  A cgo
      callback works by writing out C code that puts a struct on the stack and
      passes the address of that struct into Go.  The result parameters are
      fields of the struct.  The Go code will write to the result parameters,
      but the Go code thinks it is just writing into the Go stack, and
      therefore won't call msanwrite.  This CL adds a call to msanwrite in the
      cgo callback code so that the C knows that results were written.
      
      Change-Id: I80438dbd4561502bdee97fad3f02893a06880ee1
      Reviewed-on: https://go-review.googlesource.com/16611Reviewed-by: 's avatarDavid Crawshaw <crawshaw@golang.org>
      8f3f2cca
    • Austin Clements's avatar
      runtime: clean up park messages · f84420c2
      Austin Clements authored
      This changes "mark worker (idle)" to "GC worker (idle)" so it's more
      clear to users that these goroutines are GC-related. It changes "GC
      assist" to "GC assist wait" to make it clear that the assist is
      blocked.
      
      Change-Id: Iafbc0903c84f9250ff6bee14baac6fcd4ed5ef76
      Reviewed-on: https://go-review.googlesource.com/16511Reviewed-by: 's avatarRick Hudson <rlh@golang.org>
      f84420c2
    • Austin Clements's avatar
      runtime: free stack spans outside STW · 56ad88b1
      Austin Clements authored
      We couldn't do this before this point because it must be done before
      the next GC cycle starts. Hence, if it delayed the start of the next
      cycle, that would widen the window between reaching the heap trigger
      of the next cycle and starting the next GC cycle, during which the
      mutator could over-allocate. With the decentralized GC, any mutators
      that reach the heap trigger will block on the GC starting, so it's
      safe to widen the time between starting the world and being able to
      start the next GC cycle.
      
      Fixes #11465.
      
      Change-Id: Ic7ea7e9eba5b66fc050299f843a9c9001ad814aa
      Reviewed-on: https://go-review.googlesource.com/16394Reviewed-by: 's avatarRick Hudson <rlh@golang.org>
      Run-TryBot: Austin Clements <austin@google.com>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      56ad88b1
    • Ian Lance Taylor's avatar
      misc/cgo/test: disable Test10303 for gccgo · d841860f
      Ian Lance Taylor authored
      When using gccgo it's OK if a pointer passed to C remains on the stack.
      Gccgo does not have the clear distinction between C and Go stacks.
      
      Change-Id: I3af9dd6fe078214ab16d9d8dad2d206608d7891d
      Reviewed-on: https://go-review.googlesource.com/16774
      Run-TryBot: Ian Lance Taylor <iant@golang.org>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: 's avatarMinux Ma <minux@golang.org>
      d841860f
  2. 10 Nov, 2015 17 commits
  3. 09 Nov, 2015 6 commits
  4. 08 Nov, 2015 10 commits
  5. 07 Nov, 2015 3 commits