Ayke van Laethem e075e0591d main: use go env instead of doing all detection manually ... This replaces our own manual detection of various variables (GOROOT, GOPATH, Go version) with a simple call to `go env`. If the `go` command is not found: error: could not find 'go' command: executable file not found in $PATH If the Go version is too old: error: requires go version 1.18 through 1.20, got go1.17 If the Go tool itself outputs an error (using GOROOT=foobar here): go: cannot find GOROOT directory: foobar This does break the case where `go` wasn't available in $PATH but we would detect it anyway (via some hardcoded OS-dependent paths). I'm not sure we want to fix that: I think it's better to tell users "make sure `go version` prints the right value" than to do some automagic detection of Go binary locations.		2023-07-07 16:55:59 +02:00
..
ircheck
llvmutil
testdata	compiler: update .ll test output	2023-07-02 15:35:42 +02:00
alias.go
asserts.go
atomic.go
calls.go	fix some comments	2023-04-18 22:51:49 +02:00
channel.go
compiler.go	compiler: only calculate functionInfo once	2023-05-20 11:24:20 +02:00
compiler_test.go	main: use go env instead of doing all detection manually	2023-07-07 16:55:59 +02:00
defer.go
errors.go
func.go
gc.go
goroutine.go
inlineasm.go
interface.go	compiler,reflect: NumMethods reports exported methods only	2023-07-02 15:35:42 +02:00
interrupt.go
intrinsics.go
llvm.go
map.go
sizes.go
symbol.go	compiler: disallow most types in //go:wasmimport	2023-05-20 11:24:20 +02:00
syscall.go
volatile.go