Steps to reproduce:

• on a Macbook Pro running latest OS, compile Go at version 95b8cbf
• run go install golang.org/x/tools/... with latest x/tools version
• run go install honnef.co/go/tools/... with either the latest tagged staticcheck release or the latest commit on master.
• run staticcheck ./... on any codebase, for example github.com/kevinburke/go-bindata

I expect it to report the usual set of linter errors (or none, if the linter reports no errors). Instead I get output that looks like this:

-: could not analyze dependency crypto/rand of github.com/kevinburke/go-bindata [github.com/kevinburke/go-bindata.test]:
	could not analyze dependency errors of crypto/rand:
	could not analyze dependency internal/reflectlite of errors:
	could not analyze dependency runtime of internal/reflectlite:
	could not analyze dependency runtime/internal/math of runtime:
	could not analyze dependency runtime/internal/sys of runtime/internal/math:
	could not load export data: cannot import "runtime/internal/sys" (unknown iexport format version 1), export data is newer version - update tool (compile)

I cannot reproduce with the previous commit in the Go tree (683ef8c).

I am trying to run Go tip as my primary development environment but this is the second workflow-breaking issue I have run into in two weeks (previously #34294). I am willing to accept occasional workflow disturbances but two in two weeks that require 30-60 minutes to track down is too many.

If a change in the export data requires these tools to be updated, maybe the new versions can be released in parallel.