1. 11 Nov, 2015 2 commits
    • 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 5 commits