1. 09 Jul, 2014 5 commits
    • Aram Hăvărneanu's avatar
      cmd/objdump: set goarch properly on non-386 Plan 9 systems · fa113cf7
      Aram Hăvărneanu authored
      LGTM=0intro, r
      R=0intro, r
      CC=ality, golang-codereviews, jas, mischief
      https://golang.org/cl/108420043
      fa113cf7
    • Aram Hăvărneanu's avatar
      syscall: remove more NxM assumptions on Plan 9 · 38e75f9d
      Aram Hăvărneanu authored
      LGTM=0intro, r
      R=0intro, r
      CC=ality, dave, golang-codereviews, jas, mischief, rsc
      https://golang.org/cl/111910043
      38e75f9d
    • Aram Hăvărneanu's avatar
      os: fix failing test on Plan 9 · a6cc6347
      Aram Hăvărneanu authored
      LGTM=0intro, r
      R=0intro, r
      CC=ality, dave, golang-codereviews, jas, mischief, rsc
      https://golang.org/cl/105580044
      a6cc6347
    • Cristian Staretu's avatar
      syscall: NetlinkRIB, avoid allocation in loop · 8aea9a00
      Cristian Staretu authored
      NetlinkRIB is currently allocating a page sized slice of bytes in a
      for loop and it's also calling Getpagesize() in the same for loop.
      
      This CL changes NetlinkRIB to preallocate the page sized slice of
      bytes before reaching the for loop. This reduces memory allocations
      and lowers the number of calls to Getpagesize() to 1 per NetlinkRIB
      call.
      
      This CL reduces the allocated memory from 141.5 MB down to 52 MB in
      a test.
      
      LGTM=crawshaw, dave
      R=dave, dsymonds, crawshaw
      CC=bradfitz, dsymonds, golang-codereviews
      https://golang.org/cl/110920043
      8aea9a00
    • Dmitri Shuralyov's avatar
      cmd/go: fix build -o panic when import path pattern matches 0 pkgs · 3e801416
      Dmitri Shuralyov authored
      Fixes #8165.
      
      After this change, the panic is replaced by a message:
      
              $ go build -o out ...doesntexist
              warning: "...doesntexist" matched no packages
              no packages to build
      
      The motivation to return 1 exit error code is to allow -o flag
      to be used to guarantee that the output binary is written to
      when exit status is 0. If someone uses an import path pattern
      to specify a single package and suddenly that matches no packages,
      it's better to return exit code 1 instead of silently doing nothing.
      This is consistent with the case when -o flag is given and multiple
      packages are matched.
      It's also somewhat consistent with the current behavior with the
      panic, except that gave return code 2. But it's similar in
      that it's also non-zero (indicating failure).
      I've changed the language to be similar to output of go test
      when an import path pattern matches no packages (it also has a return status of
      1):
      
              $ go test ...doesntexist
              warning: "...doesntexist" matched no packages
              no packages to test
      
      LGTM=adg
      R=golang-codereviews, josharian, gobot, adg
      CC=golang-codereviews
      https://golang.org/cl/107140043
      3e801416
  2. 08 Jul, 2014 14 commits
  3. 07 Jul, 2014 4 commits
  4. 05 Jul, 2014 2 commits
  5. 04 Jul, 2014 1 commit
  6. 03 Jul, 2014 6 commits
  7. 02 Jul, 2014 8 commits