cmd/go: allow -fsanitize-undefined-strip-path-components

[zecke]

Go version

go version go1.23.3 darwin/arm64

Output of go env in your module/workspace:

<snip>

What did you do?

I am using bazel with the rules_go, gazelle and hermetic_cc_toolchain bazel modules (bzlmod) to build an application. The application is allowed to rely on cgo (e.g. os/user)

What did you see happen?

The final binary was linked with the linker provided by hermetic_cc_toolchain and not Go's internal linker.

What did you expect to see?

I expected this to be linked with Go's linker. In this case it matters as there is a significant difference in linking speed.

[zecke]

The relevant flag leading to this behavior appears to be -fsanitize-undefined-strip-path-components=N and it controls stripping path information from the internal UndefinedBehaviorSanitizer

[seankhliao]

This looks like an issue for hermetic_cc_toolchain, not Go.

[gopherbot]

Change https://go.dev/cl/657575 mentions this issue: cmd/go: permit additional cflags when compiling