Change to dir before running the command. Any files named on the command line are interpreted after changing directories. If used, this flag must be the first one in the command line.

force rebuilding of packages that are already up-to-date.

print the commands but do not run them.

the number of programs, such as build commands or test binaries, that can be run in parallel.

The default is GOMAXPROCS, normally the number of CPUs available.

enable data race detection.

Supported only on darwin/amd64, darwin/arm64, freebsd/amd64, linux/amd64, linux/arm64 (only for 48-bit VMA), linux/ppc64le, linux/riscv64 and windows/amd64.

enable interoperation with memory sanitizer.

Supported only on linux/amd64, linux/arm64, linux/loong64, freebsd/amd64 and only with Clang/LLVM as the host C compiler. PIE build mode will be used on all platforms except linux/amd64.

enable interoperation with address sanitizer.

Supported only on linux/arm64, linux/amd64, linux/loong64.

Supported on linux/amd64 or linux/arm64 and only with GCC 7 and higher or Clang/LLVM 9 and higher.

And supported on linux/loong64 only with Clang/LLVM 16 and higher.

enable code coverage instrumentation.

set the mode for coverage analysis. The default is “set” unless -race is enabled, in which case it is “atomic”.

The values:

set: bool: does this statement run?

count: int: how many times does this statement run?

atomic: int: count, but correct in multithreaded tests; significantly more expensive.

Sets -cover.

For a build that targets package `main' (e.g. building a Go executable), apply coverage analysis to each package whose import path matches the patterns. The default is to apply coverage analysis to packages in the main Go module. See `go help packages' for a description of package patterns. Sets -cover.

print the names of packages as they are compiled.

print the name of the temporary work directory and do not delete it when exiting.

print the commands.

arguments to pass on each go tool asm invocation.

build mode to use. See `go help buildmode' for more.

Whether to stamp binaries with version control information (“true”, “false”, or “auto”). By default (“auto”), version control information is stamped into a binary if the main package, the main module containing it, and the current directory are all in the same repository. Use -buildvcs=false to always omit version control information, or -buildvcs=true to error out if version control information is available but cannot be included due to a missing tool or ambiguous directory structure.

name of compiler to use, as in runtime.Compiler (gccgo or gc).

arguments to pass on each gccgo compiler/linker invocation.

arguments to pass on each go tool compile invocation.

a suffix to use in the name of the package installation directory, in order to keep output separate from default builds. If using the -race flag, the install suffix is automatically set to race or, if set explicitly, has _race appended to it. Likewise for the -msan and -asan flags. Using a -buildmode option that requires non-default compile flags has a similar effect.

Emit build output in JSON suitable for automated processing. See `go help buildjson' for the encoding details.

arguments to pass on each go tool link invocation.

build code that will be linked against shared libraries previously created with -buildmode=shared.

module download mode to use: readonly, vendor, or mod. By default, if a vendor directory is present and the go version in go.mod is 1.14 or higher, the go command acts as if -mod=vendor were set. Otherwise, the go command acts as if -mod=readonly were set.

See https://golang.org/ref/mod#build-commands for details.

leave newly-created directories in the module cache read-write instead of making them read-only.

in module aware mode, read (and possibly write) an alternate go.mod file instead of the one in the module root directory. A file named “go.mod” must still be present in order to determine the module root directory, but it is not accessed. When -modfile is specified, an alternate go.sum file is also used: its path is derived from the -modfile flag by trimming the “.mod” extension and appending “.sum”.

read a JSON config file that provides an overlay for build operations. The file is a JSON object with a single field, named `Replace', that maps each disk file path (a string) to its backing file path, so that a build will run as if the disk file path exists with the contents given by the backing file paths, or as if the disk file path does not exist if its backing file path is empty. Support for the -overlay flag has some limitations: importantly, cgo files included from outside the include path must be in the same directory as the Go package they are included from, overlays will not appear when binaries and tests are run through go run and go test respectively, and files beneath GOMODCACHE may not be replaced.

specify the file path of a profile for profile-guided optimization (PGO). When the special name “auto” is specified, for each main package in the build, the go command selects a file named “default.pgo” in the package’s directory if that file exists, and applies it to the (transitive) dependencies of the main package (other packages are not affected). Special name “off” turns off PGO. The default is “auto”.

install and load all packages from dir instead of the usual locations. For example, when building with a non-standard configuration, use -pkgdir to keep generated packages in a separate location.

a comma-separated list of additional build tags to consider satisfied during the build. For more information about build tags, see `go help buildconstraint'. (Earlier versions of Go used a space-separated list, and that form is deprecated but still recognized.)

remove all file system paths from the resulting executable. Instead of absolute file system paths, the recorded file names will begin either a module path@version (when using modules), or a plain import path (when using the standard library, or GOPATH).

a program to use to invoke toolchain programs like vet and asm. For example, instead of running asm, the go command will run `cmd args /path/to/asm <arguments for asm>'. The TOOLEXEC_IMPORTPATH environment variable will be set, matching `go list -f {{.ImportPath}}' for the package being built.