github/golang.go
2
0
Fork 0
mirror of https://github.com/golang/go.git synced 2026-04-03 09:49:56 +09:00
Code Issues Packages Projects Releases Wiki Activity
Files
master
golang.go/doc/next/3-tools.md
Michael Podtserkovskii 4b7b1be731 cmd/internal/objabi: implement GCC-compatible response file parsing 
Replace line-based response file parsing with GCC-compatible one
that supports:
- Whitespace-delimited arguments (multiple args per line)
- Single quotes for literal content (no escape processing)
- Double quotes with escape sequences: \\, \", \$, \`
- Backslash-newline line continuation (both LF and CRLF)

Update encodeArg in cmd/go/internal/work to produce GCC-compatible
output with proper escaping of special characters.

Add response file support to cmd/pack.

For #77177

Change-Id: Ib8dbe2761ebe139b3949dcaeb1de4bb5b15ddabb
Reviewed-on: https://go-review.googlesource.com/c/go/+/737500
Reviewed-by: Carlos Amedee <carlos@golang.org>
Reviewed-by: Mark Freeman <markfreeman@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Michael Matloob <matloob@golang.org>
Reviewed-by: Alex Brainman <alex.brainman@gmail.com>
2026-03-18 19:58:52 -07:00

757 B
Raw Permalink Blame History

Tools

Response file (@file) parsing is now supported for the compile, link, asm, cgo, cover, and pack tools. The response file contains whitespace-separated arguments with support for single-quoted and double-quoted strings, escape sequences, and backslash-newline line continuation. The format is compatible with GCC's response file implementation to ensure interoperability with existing build systems.

Go command

go test now invokes the stdversion vet check by default. This reports the use of standard library symbols that are too new for the Go version in force in the referring file, as determined by go directive in go.mod and build tags on the file.

Cgo