1. 07 Mar, 2019 7 commits
  2. 06 Mar, 2019 30 commits
  3. 05 Mar, 2019 3 commits
    • Agniva De Sarker's avatar
      go/doc: add // while wrapping a line comment in ToText · e90f572c
      Agniva De Sarker authored
      Currently, lineWrapper does not detect if it is printing a line comment or not.
      Hence, while wrapping a comment, the new line does not get prefixed with a //.
      
      We add logic to lineWrapper to detect this case and add // accordingly. Block
      comments do not need any such handling.
      
      Added tests for both cases.
      
      Fixes #20929
      
      Change-Id: I656037c2d865f31dd853cf9195f43ab7c6e6fc53
      Reviewed-on: https://go-review.googlesource.com/c/go/+/163578
      Run-TryBot: Robert Griesemer <gri@golang.org>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: default avatarRobert Griesemer <gri@golang.org>
      e90f572c
    • Austin Clements's avatar
      runtime: introduce effective GOGC, eliminate heap_marked hacks · 5c22842c
      Austin Clements authored
      Currently, the pacer assumes the goal growth ratio is always exactly
      GOGC/100. But sometimes this isn't the case, like when the heap is
      very small (limited by heapminimum). So to placate the pacer, we lie
      about the value of heap_marked in such situations.
      
      Right now, these two lies make a truth, but GOGC is about to get more
      complicated with the introduction of heap limits.
      
      Rather than introduce more lies into the system to handle this,
      introduce the concept of an "effective GOGC", which is the GOGC we're
      actually using for pacing (we'll need this concept anyway with heap
      limits). This commit changes the pacer to use the effective GOGC
      rather than the user-set GOGC. This way, we no longer need to lie
      about heap_marked because its true value is incorporated into the
      effective GOGC.
      
      Change-Id: I5b005258f937ab184ffcb5e76053abd798d542bd
      Reviewed-on: https://go-review.googlesource.com/c/go/+/66092
      Run-TryBot: Austin Clements <austin@google.com>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: default avatarMichael Knyszek <mknyszek@google.com>
      Reviewed-by: default avatarRick Hudson <rlh@golang.org>
      5c22842c
    • Austin Clements's avatar
      runtime: don't use GOGC in minimum sweep distance · 4a7d5aa3
      Austin Clements authored
      Currently, the minimum sweep distance is 1MB * GOGC/100. It's been
      this way since it was introduced in CL 13043 with no justification.
      
      Since there seems to be no good reason to scale the minimum sweep
      distance by GOGC, make the minimum sweep distance just 1MB.
      
      Change-Id: I5320574a23c0eec641e346282aab08a3bbb057da
      Reviewed-on: https://go-review.googlesource.com/c/go/+/66091
      Run-TryBot: Austin Clements <austin@google.com>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: default avatarMichael Knyszek <mknyszek@google.com>
      Reviewed-by: default avatarRick Hudson <rlh@golang.org>
      4a7d5aa3