1. 02 Feb, 2016 2 commits
  2. 01 Feb, 2016 1 commit
  3. 31 Jan, 2016 1 commit
  4. 30 Jan, 2016 1 commit
    • Todd Neal's avatar
      [dev.ssa] cmd/compile: reuse sparse sets across compiler passes · f962f330
      Todd Neal authored
      Cache sparse sets in the function so they can be reused by subsequent
      compiler passes.
      
      benchmark                        old ns/op     new ns/op     delta
      BenchmarkDSEPass-8               206945        180022        -13.01%
      BenchmarkDSEPassBlock-8          5286103       2614054       -50.55%
      BenchmarkCSEPass-8               1790277       1790655       +0.02%
      BenchmarkCSEPassBlock-8          18083588      18112771      +0.16%
      BenchmarkDeadcodePass-8          59837         41375         -30.85%
      BenchmarkDeadcodePassBlock-8     1651575       511169        -69.05%
      BenchmarkMultiPass-8             531529        427506        -19.57%
      BenchmarkMultiPassBlock-8        7033496       4487814       -36.19%
      
      benchmark                        old allocs     new allocs     delta
      BenchmarkDSEPass-8               11             4              -63.64%
      BenchmarkDSEPassBlock-8          599            120            -79.97%
      BenchmarkCSEPass-8               18             18             +0.00%
      BenchmarkCSEPassBlock-8          2700           2700           +0.00%
      BenchmarkDeadcodePass-8          4              3              -25.00%
      BenchmarkDeadcodePassBlock-8     30             9              -70.00%
      BenchmarkMultiPass-8             24             20             -16.67%
      BenchmarkMultiPassBlock-8        1800           1000           -44.44%
      
      benchmark                        old bytes     new bytes     delta
      BenchmarkDSEPass-8               221367        142           -99.94%
      BenchmarkDSEPassBlock-8          3695207       3846          -99.90%
      BenchmarkCSEPass-8               303328        303328        +0.00%
      BenchmarkCSEPassBlock-8          5006400       5006400       +0.00%
      BenchmarkDeadcodePass-8          84232         10506         -87.53%
      BenchmarkDeadcodePassBlock-8     1274940       163680        -87.16%
      BenchmarkMultiPass-8             608674        313834        -48.44%
      BenchmarkMultiPassBlock-8        9906001       5003450       -49.49%
      
      Change-Id: Ib1fa58c7f494b374d1a4bb9cffbc2c48377b59d3
      Reviewed-on: https://go-review.googlesource.com/19100Reviewed-by: 's avatarDavid Chase <drchase@google.com>
      Reviewed-by: 's avatarKeith Randall <khr@golang.org>
      f962f330
  5. 29 Jan, 2016 9 commits
  6. 28 Jan, 2016 2 commits
  7. 26 Jan, 2016 2 commits
  8. 22 Jan, 2016 1 commit
  9. 21 Jan, 2016 1 commit
  10. 20 Jan, 2016 2 commits
  11. 19 Jan, 2016 6 commits
  12. 18 Jan, 2016 6 commits
  13. 16 Jan, 2016 3 commits
  14. 15 Jan, 2016 3 commits
    • Brad Fitzpatrick's avatar
      net/http: update bundled http2 · 91b910b7
      Brad Fitzpatrick authored
      If a user starts two HTTP requests when no http2 connection is
      available, both end up creating new TCP connections, since the
      server's protocol (h1 or h2) isn't yet known. Once it turns out that
      the server supports h2, one of the connections is useless. Previously
      we kept upgrading both TLS connections to h2 (SETTINGS frame exchange,
      etc).  Now the unnecessary connections are closed instead, before the
      h2 preface/SETTINGS.
      
      Updates x/net/http2 to git rev a8e212f3d for https://golang.org/cl/18675
      
      This CL contains the tests for https://golang.org/cl/18675
      
      Semi-related change noticed while writing the tests: now that we have
      TLSNextProto in Go 1.6, which consults the TLS
      ConnectionState.NegotiatedProtocol, we have to gurantee that the TLS
      handshake has been done before we look at the ConnectionState. So add
      that check after the DialTLS hook. (we never documented that users
      have to call Handshake, so do it for them, now that it matters)
      
      Updates #13957
      
      Change-Id: I9a70e9d1282fe937ea654d9b1269c984c4e366c0
      Reviewed-on: https://go-review.googlesource.com/18676Reviewed-by: 's avatarAndrew Gerrand <adg@golang.org>
      Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      91b910b7
    • Keith Randall's avatar
      [dev.ssa] runtime: fix windows build · 594c3aa0
      Keith Randall authored
      Pull the relevant part of https://go-review.googlesource.com/#/c/18304/
      into the SSA branch.  This fixes the windows SSA build.
      
      Change-Id: Iee3834d8e7019cd90307e32029f3d1032ceb46c1
      Reviewed-on: https://go-review.googlesource.com/18673Reviewed-by: 's avatarAustin Clements <austin@google.com>
      594c3aa0
    • Austin Clements's avatar
      runtime: use at least "system" traceback level for runtime tests · 1556c317
      Austin Clements authored
      While the default behavior of eliding runtime frames from tracebacks
      usually makes sense, this is not the case when you're trying to test
      the runtime itself. Fix this by forcing the traceback level to at
      least "system" in the runtime tests.
      
      This will specifically help with debugging issue #13645, which has
      proven remarkably resistant to reproduction outside of the build
      dashboard itself.
      
      Change-Id: I2a8356ba6c3c5badba8bb3330fc527357ec0d296
      Reviewed-on: https://go-review.googlesource.com/18648
      Run-TryBot: Austin Clements <austin@google.com>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: 's avatarAlex Brainman <alex.brainman@gmail.com>
      1556c317