Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
proposal: doc: document that Go 1.14 is last to support darwin/386? #34749
macOS Catalina does not support running 32-bit apps.
Time to remove darwin/386 support soon? (@rsc always liked keeping it around as an easy way to hack on the 386 port on his laptop, but sounds like that reason is going away. We might even be able to remove it earlier, once Russ upgrades his laptop.)
Might be worth noting that it's going away soon in the Go 1.14 release notes.
Does hacking on a port require being able to run the binaries, or just test that it compiles? If the latter, it'll still be possible to use something like
I opened a related proposal #34751 that's about
Brad, do you have an idea of the benefits of removing
Anything I'm missing?
Asking these questions in order to have more information and to be able to evaluate this proposal better.
It's much less code & less weirdness than nacl. At least these files:
But also stuff in debug/macho, cmd/link, etc.
So, there are non-zero costs.
What are the reasons to keep it? The one reason we had is going away in the next ~month (when our primary runtime/compiler people update their laptops).
And in a couple more years it won't even be possible to run a darwin/386 binary on any supported Go build.