1. 12 Nov, 2018 2 commits
    • Austin Clements's avatar
      internal/bytealg, runtime: provide linknames for pushed symbols · ef7ce57a
      Austin Clements authored
      The internal/bytealg package defines several symbols in the runtime,
      bytes, and strings packages in assembly, and the runtime package
      defines symbols in reflect and sync/atomic. Currently, there's no
      corresponding Go prototype for these symbols in the defining package.
      
      We're going to start depending on Go prototypes in the same package as
      their assembly definitions in order to provide ABI wrappers. Plus,
      these are good documentation and colocate type information with
      definitions, which could be useful for vet if it learned a little
      about linkname.
      
      This CL adds linknamed Go prototypes for all pushed symbols in
      internal/bytealg and runtime.
      
      For #27539.
      
      Change-Id: I9b0c12d935a75bb6af46b6761180d451c00f11b8
      Reviewed-on: https://go-review.googlesource.com/c/146820
      Run-TryBot: Austin Clements <austin@google.com>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: 's avatarKeith Randall <khr@golang.org>
      Reviewed-by: 's avatarMichael Knyszek <mknyszek@google.com>
      ef7ce57a
    • Austin Clements's avatar
      runtime, reflect: access runtime.reflectcall directly · 4f3604d3
      Austin Clements authored
      Currently, package runtime contains the definition of reflect.call,
      even though it's just a jump to runtime.reflectcall. This "push"
      symbol is confusing, since it's not clear where the definition of
      reflect.call comes from when you're in the reflect package.
      
      Replace this with a "pull" symbol: the runtime now defines only
      runtime.reflectcall and package reflect uses a go:linkname to access
      this symbol directly. This makes it clear where reflect.call is coming
      from without any spooky action at a distance and eliminates all of the
      definitions of reflect.call in the runtime.
      
      Change-Id: I3ec73cd394efe9df8d3061a57c73aece2e7048dd
      Reviewed-on: https://go-review.googlesource.com/c/148657
      Run-TryBot: Austin Clements <austin@google.com>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: 's avatarBrad Fitzpatrick <bradfitz@golang.org>
      Reviewed-by: 's avatarKeith Randall <khr@golang.org>
      4f3604d3
  2. 11 Nov, 2018 4 commits
    • Ainar Garipov's avatar
      go/build: remove superfluous continues · f58b02a2
      Ainar Garipov authored
      This cleanup was proposed in CL 148937. The branch is already ended with
      a continue, so remove continues from subbranches and use an else-if.
      
      Change-Id: Iaf6eb57afc84e25862f99a342f5824e315bcdcb7
      Reviewed-on: https://go-review.googlesource.com/c/148922Reviewed-by: 's avatarBrad Fitzpatrick <bradfitz@golang.org>
      f58b02a2
    • Michael Anthony Knyszek's avatar
      runtime: gofmt all improperly formatted code · 3a7a56cc
      Michael Anthony Knyszek authored
      This change fixes incorrect formatting in mheap.go (the result of my
      previous heap scavenging changes) and map_test.go.
      
      Change-Id: I2963687504abdc4f0cdf2f0c558174b3bc0ed2df
      Reviewed-on: https://go-review.googlesource.com/c/148977
      Run-TryBot: Michael Knyszek <mknyszek@google.com>
      Reviewed-by: 's avatarAustin Clements <austin@google.com>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      3a7a56cc
    • Josh Bleecher Snyder's avatar
      cmd/compile: optimize A->B->C Moves that include VarDefs · 8607b2e8
      Josh Bleecher Snyder authored
      We have an existing optimization that recognizes
      memory moves of the form A -> B -> C and converts
      them into A -> C, in the hopes that the store to
      B will be end up being dead and thus eliminated.
      
      However, when A, B, and C are large types,
      the front end sometimes emits VarDef ops for the moves.
      This change adds an optimization to match that pattern.
      
      This required changing an old compiler test.
      The test assumed that a temporary was required
      to deal with a large return value.
      With this optimization in place, that temporary
      ended up being eliminated.
      
      Triggers 649 times during 'go build -a std cmd'.
      
      Cuts 16k off cmd/go.
      
      name        old object-bytes  new object-bytes  delta
      Template          507kB ± 0%        507kB ± 0%  -0.15%  (p=0.008 n=5+5)
      Unicode           225kB ± 0%        225kB ± 0%    ~     (all equal)
      GoTypes          1.85MB ± 0%       1.85MB ± 0%    ~     (all equal)
      Flate             328kB ± 0%        328kB ± 0%    ~     (all equal)
      GoParser          402kB ± 0%        402kB ± 0%  -0.00%  (p=0.008 n=5+5)
      Reflect          1.41MB ± 0%       1.41MB ± 0%  -0.20%  (p=0.008 n=5+5)
      Tar               458kB ± 0%        458kB ± 0%    ~     (all equal)
      XML               601kB ± 0%        599kB ± 0%  -0.21%  (p=0.008 n=5+5)
      
      Change-Id: I9b5f25c8663a0b772ad1ee51fa61f74b74d26dd3
      Reviewed-on: https://go-review.googlesource.com/c/143479
      Run-TryBot: Josh Bleecher Snyder <josharian@gmail.com>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      Reviewed-by: 's avatarMichael Munday <mike.munday@ibm.com>
      8607b2e8
    • Ainar Garipov's avatar
      go/build, go/doc: fix tautological conditions · f9fff455
      Ainar Garipov authored
      These issues were found by the new vet's nilness check. The variables
      were already checked against nil, so remove extra checks.
      
      Change-Id: Ie252ccfcc755f3d06f691f354bf13d5a623fe17b
      Reviewed-on: https://go-review.googlesource.com/c/148937Reviewed-by: 's avatarRobert Griesemer <gri@golang.org>
      Run-TryBot: Robert Griesemer <gri@golang.org>
      TryBot-Result: Gobot Gobot <gobot@golang.org>
      f9fff455
  3. 10 Nov, 2018 7 commits
  4. 09 Nov, 2018 16 commits
  5. 08 Nov, 2018 11 commits