cmd/link: issues with Xcode 16 beta [1.22 backport] about go HOT 7 CLOSED

Go 1.21 will be out of support soon, certainly before Xcode 16 is released. So I don't think we need to do Go 1.21.

from go.

Similar Issues

• cmd/link: issues with Apple's new linker in Xcode 15 beta [1.20 backport] #62597
• cmd/link: issues with Apple's new linker in Xcode 15 beta [1.21 backport] #62598
• runtime/race: building for iOS, but linking in object file built for macOS [1.16 backport] #50194

_{(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)}

from go.

@cherrymui agreed to approve , however please create backport for 1.21 as well.

from go.

however please create backport for 1.21 as well.

As commented above #68198 (comment) I don't think we need to backport to Go 1.21. Could you explain why that is necessary? Thanks.

from go.

Our default policy decision is to support all supported versions of Go equally. See accepted proposal 34536. Since this problem affects both Go 1.22 and 1.21, it seemed that 1.21 should get the fix too.

I was going to suggest that if backporting to Go 1.21 creates unreasonable overhead, it's likely fine to wait a bit while Xcode 16 is still in beta, and revisit this after Go 1.23.0 is out, but I understand you were making the same point in #68198 (comment) in that the problem isn't there now, but in the future, and by then 1.23 and 1.22 will be supported. So I think it is indeed okay to move forward with 1.22 only from that perspective. Thanks.

from go.

Change https://go.dev/cl/596455 mentions this issue: [release-branch.go1.22] cmd/link: don't let dsymutil delete our temp directory

from go.

Closed by merging 4e548f2 to release-branch.go1.22.

from go.