1. 17 Jun, 2015 19 commits
  2. 16 Jun, 2015 15 commits
  3. 15 Jun, 2015 6 commits
    • Robert Griesemer's avatar
      go/types: fix Eval to use correct file set when evaluating an expression · 7322ef5d
      Robert Griesemer authored
      This is https://go-review.googlesource.com/10999 which we could not apply
      in x/tools/go/types because we must not rely on 1.5 features in that repo
      yet.
      
      Change-Id: I9a57cdb7ad4051df278d1fbed90c736df50f426f
      Reviewed-on: https://go-review.googlesource.com/11125Reviewed-by: 's avatarAlan Donovan <adonovan@google.com>
      7322ef5d
    • Robert Griesemer's avatar
      go/types: port recent x/tools/go/types fixes · d63c42df
      Robert Griesemer authored
      The main change is:
      
      golang.org/cl/10800  add pos parameter to Eval; remove New, EvalNode
      
      followed by several cleanups/follow-up fixes:
      
      golang.org/cl/10992  remove global vars in test
      golang.org/cl/10994  remove unused scope parameter from NewSignature
      golang.org/cl/10995  provide full source file extent to file scope
      golang.org/cl/10996  comment fix in resolver.go
      golang.org/cl/11004  updated cmd/vet
      golang.org/cl/11042  be robust in the presence of incorrect/missing position info
      
      Fixes #9980.
      
      Change-Id: Id4aff688f6a399f76bf92b84c7e793b8da8baa48
      Reviewed-on: https://go-review.googlesource.com/11122Reviewed-by: 's avatarAlan Donovan <adonovan@google.com>
      d63c42df
    • Brad Fitzpatrick's avatar
      cmd/go: fix typo · 4965a77f
      Brad Fitzpatrick authored
      Change-Id: I171a1125e25b13c934c2cd545bd03f49f642910d
      Reviewed-on: https://go-review.googlesource.com/11113Reviewed-by: 's avatarIan Lance Taylor <iant@golang.org>
      4965a77f
    • Ian Lance Taylor's avatar
      syscall: fix TestCloneNEWUSERAndRemapNoRootDisableSetgroups the right way · 6f0e4272
      Ian Lance Taylor authored
      The problem was not the kernel version as I thought before, it was
      that the test used the same number for both the UID and the GID.
      Thanks to Chris Siebenmann for debugging this.
      
      Fixes #11220.
      
      Change-Id: Ib5077e182497155e84044683209590ee0f7c9dde
      Reviewed-on: https://go-review.googlesource.com/11124Reviewed-by: 's avatarBrad Fitzpatrick <bradfitz@golang.org>
      Reviewed-by: 's avatarAustin Clements <austin@google.com>
      6f0e4272
    • Russ Cox's avatar
      cmd/go: make -a apply to the standard library, like in Go 1.3 · 4dab6d01
      Russ Cox authored
      This CL adds a very long comment explaining how isStale and
      the new build IDs work. As part of writing the comment I realized:
      
      // When the go command makes the wrong build decision and does not
      // rebuild something it should, users fall back to adding the -a flag.
      // Any common use of the -a flag should be considered prima facie evidence
      // that isStale is returning an incorrect false result in some important case.
      // Bugs reported in the behavior of -a itself should prompt the question
      // ``Why is -a being used at all? What bug does that indicate?''
      
      The two uses of -a that are most commonly mentioned in bugs filed
      against the go command are:
      
      	go install -a ./...
      	go build -tags netgo -a myprog
      
      Both of these commands now do the right thing without needing -a.
      
      The -a exception we introduced in Go 1.4 was for the first form, and
      it broke the second form. Again, neither needs -a anymore, so restore
      the old, simpler, easier to explain, less surprising meaning used in Go 1.3:
      if -a is given, rebuild EVERYTHING.
      
      See the comment for more justification and history.
      
      Summary of recent CLs (to link bugs to this one):
      
      Fixes #3036. Now 'go install ./...' works.
      Fixes #6534. Now 'go install ./...' works.
      Fixes #8290. Now 'go install ./...' works.
      Fixes #9369. Now 'go build -tags netgo myprog' works.
      Fixes #10702. Now using one GOPATH with Go 1.5 and Go 1.6 works.
        (Each time you switch, everything needed gets rebuilt.
        Switching from Go 1.4 to Go 1.5 will rebuild properly.
        Switching from Go 1.5 back to Go 1.4 still needs -a when
        invoking the Go 1.4 go command.)
      
      Change-Id: I19f9eb5286efaa50de7c8326602e94604ab572eb
      Reviewed-on: https://go-review.googlesource.com/10761Reviewed-by: 's avatarIan Lance Taylor <iant@golang.org>
      4dab6d01
    • Russ Cox's avatar
      cmd/go: include Go toolchain information in build ID · 3ab9ff11
      Russ Cox authored
      This causes packages and binaries built by Go 1.5 to look
      out of date to Go 1.6 and vice versa, so that when you flip
      between different Go versions but keep the same GOPATH,
      the right rebuilding happens at each flip.
      
      Go 1.4 binaries will also look out of date to Go 1.5,
      but Go 1.5 binaries will not look out of date to Go 1.4
      (since Go 1.4 doesn't have anything like this).
      People flipping between Go 1.4 and Go 1.5 will still
      need to use go install -a every time to flip to Go 1.4,
      but not when they flip back to Go 1.5.
      
      Fixes #6534.
      Fixes #10702.
      
      Change-Id: I0ae7f268f822d483059a938a4f22846ff9275b4c
      Reviewed-on: https://go-review.googlesource.com/10760Reviewed-by: 's avatarIan Lance Taylor <iant@golang.org>
      Reviewed-by: 's avatarAndrew Gerrand <adg@golang.org>
      3ab9ff11