-
Notifications
You must be signed in to change notification settings - Fork 17.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
all: remove darwin/386 #37610
Comments
Just a note that I don't think we should remove any 386 support from debug/macho. The debug/macho package is for analyzing Mach-O files, and we should continue to support examining Mach-O 386 files even if we can no longer generate them. |
@ianlancetaylor sgtm. Thanks for the note. |
Can we drop the darwin/386 builders from tip? I am failing them in CL 227037 but it's not worth fixing them since we are dropping the target. |
Change https://golang.org/cl/226985 mentions this issue: |
Change https://golang.org/cl/227181 mentions this issue: |
@FiloSottile Yes, we should stop running those builders on tip (but they should still run on 1.14 and older release branches). The I see @bradfitz already sent CL 226985 for that. If you want, you could rebase your CL on top to test it. |
This only removes the ability to build it, and removes it as a src/buildall.bash target (which uses go tool dist list). Now: $ go tool dist list | grep ^darwin darwin/amd64 darwin/arm64 After this, remaining is removing leftover port--specific code in the tree. Updates #37610 Updates #37611 Change-Id: I00f03b2355c2e152f75e57abd3063be243529d2d Reviewed-on: https://go-review.googlesource.com/c/go/+/226985 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Filippo Valsorda <filippo@golang.org>
The 32-bit pairs darwin/386 and darwin/arm are removed in Go 1.15, and the master branch is where Go 1.15 is being developed. The builder has started to fail after CL 226985 (as intended), so remove it. Keep it running on Go 1.14 and 1.13 release branches. Also update the misc-compile-darwin builder description. For golang/go#37610. For golang/go#37611. Change-Id: Ia70386c5ae2821b4397048dcb0862a066463d6de Reviewed-on: https://go-review.googlesource.com/c/build/+/227181 Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Andrew Bonventre <andybons@golang.org>
Change https://golang.org/cl/227582 mentions this issue: |
Change https://golang.org/cl/227581 mentions this issue: |
This removes all files that are only used on darwin/386 and cleans up build tags in files that are still used on other platforms. Updates #37610. Change-Id: If246642476c12d15f59a474e2b91a29c0c02fe75 Reviewed-on: https://go-review.googlesource.com/c/go/+/227581 Run-TryBot: Austin Clements <austin@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org> Reviewed-by: Cherry Zhang <cherryyz@google.com>
Change https://golang.org/cl/227552 mentions this issue: |
Change https://golang.org/cl/227763 mentions this issue: |
Change https://golang.org/cl/227766 mentions this issue: |
In Go 1.15, the darwin/386 port is gone. Updates #37610. Change-Id: I11627c03403d4d4a3e0950fdedd0d850ae24b439 Reviewed-on: https://go-review.googlesource.com/c/go/+/227766 Run-TryBot: Cherry Zhang <cherryyz@google.com> Reviewed-by: Austin Clements <austin@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
In Go 1.15, the darwin/386 port is gone. Updates #37610. Change-Id: I308561848d90d9a649b3603ab1f7fc1117305ec1 Reviewed-on: https://go-review.googlesource.com/c/go/+/227763 Run-TryBot: Cherry Zhang <cherryyz@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Austin Clements <austin@google.com>
The darwin/386 port has been removed per golang.org/issue/37610. TestSizes needs an operating system that has both amd64 and 386 ports, so darwin no longer qualifies. NetBSD has had its 386 port restored recently in golang/go#31726, so it can be used instead. Fixes golang/go#38319. For golang/go#37610. Change-Id: I37ce6d86ca3ddad43e9294e0de66f36091cba54a Reviewed-on: https://go-review.googlesource.com/c/tools/+/227552 Reviewed-by: Benny Siegert <bsiegert@gmail.com>
Change https://golang.org/cl/229323 mentions this issue: |
…rm code Updates #37610, #37611. Change-Id: I0a497af03e24ddea40ed3e342f3a9362bf21ac0c Reviewed-on: https://go-review.googlesource.com/c/go/+/229323 Run-TryBot: Cherry Zhang <cherryyz@google.com> Reviewed-by: Austin Clements <austin@google.com>
…rm code Updates golang#37610, golang#37611. Change-Id: I0a497af03e24ddea40ed3e342f3a9362bf21ac0c Reviewed-on: https://go-review.googlesource.com/c/go/+/229323 Run-TryBot: Cherry Zhang <cherryyz@google.com> Reviewed-by: Austin Clements <austin@google.com>
Removed in go1.15 (GH/golang/go/issues/37610). Signed-off-by: Stephen Augustus <saugustus@vmware.com>
[Go no longer supports darwin/386 (MacOS 32-bit apps), as of Go 1.15][1] [1]: golang/go#37610
[Go no longer supports darwin/386 (MacOS 32-bit apps), as of Go 1.15][1] [1]: golang/go#37610
[Go no longer supports darwin/386 (MacOS 32-bit apps), as of Go 1.15][1] [1]: golang/go#37610
Remove darwin/386 due to golang/go#37610
Remove darwin/386 due to golang/go#37610
[Go no longer supports darwin/386 (MacOS 32-bit apps), as of Go 1.15][1] [1]: golang/go#37610
Go 1.15 drops support for darwin/386 GOOS/GOARCH pair [1]. So, we have to skip this pair, and thus cannot use simple os multiply arch anymore. Switch to goxc's BuildConstraints config, which uses the same syntax as Go's build constraint header [2]. [1] golang/go#37610 [2] https://golang.org/cmd/go/#hdr-Build_constraints
Go 1.15 drops support for darwin/386 GOOS/GOARCH pair [1]. So, we have to skip this pair, and thus cannot use simple os multiply arch anymore. Switch to goxc's BuildConstraints config, which uses the same syntax as Go's build constraint header [2]. [1] golang/go#37610 [2] https://golang.org/cmd/go/#hdr-Build_constraints
Per #34749, we’re going to remove darwin/386 for Go 1.15. This is a tracking issue for that work.
Some affected files (taken from above issue. Thanks, @bradfitz):
But also stuff in
debug/macho(see below comment), cmd/link, etc.The text was updated successfully, but these errors were encountered: