- Sort Score
- Result 10 results
- Languages All
Results 1 - 2 of 2 for Gccgoflags (0.41 sec)
-
src/cmd/go/testdata/script/version_build_settings.txt
stdout '^\tbuild\t-ldflags=example\.com/m=-w$' go build -trimpath go version -m m$GOEXE stdout '\tbuild\t-trimpath=true$' # gccgoflags are not added when gc is used, and vice versa. # TODO: test gccgo. go build -gccgoflags=all=UNUSED go version -m m$GOEXE ! stdout gccgoflags # Build and tool tags are added but not release tags. # "race" is included with build tags but not "cgo". go build -tags=a,b
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Mon Oct 24 21:26:10 UTC 2022 - 2.7K bytes - Viewed (0) -
src/cmd/go/internal/load/flag.go
"fmt" "strings" ) var ( BuildAsmflags PerPackageFlag // -asmflags BuildGcflags PerPackageFlag // -gcflags BuildLdflags PerPackageFlag // -ldflags BuildGccgoflags PerPackageFlag // -gccgoflags ) // A PerPackageFlag is a command-line flag implementation (a flag.Value) // that allows specifying different effective flags for different packages. // See 'go help build' for more details about per-package flags.
Registered: Wed Jun 12 16:32:35 UTC 2024 - Last Modified: Thu May 19 20:20:43 UTC 2022 - 2.6K bytes - Viewed (0)