x/all: gccgo support #31436
Labels
NeedsDecision
Feedback is required from experts, contributors, and/or the community before a change can be made.
Milestone
Comments
bcmills
added
the
NeedsDecision
|
CC @thanm |
|
At present we have no formal testing that the x/ packages work with gccgo. In general we have no formal testing of gccgo at all. Yes, it would be nice to fix this. That said, most of the x/ packages do work with gccgo. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #31382, @mikioh asks an interesting questions about the maintenance of golang.org/x packages on gccgo.
How are we sure that the changes made in golang.org/x will work on gccgo ?
For Go toolchain, they are builders on every GOOS/GOARCH which check that it's working but what about the Gccgo toolchain ? Do we assume that if it works on Go, it must work on Gccgo ?
The core code of each package should indeed work, after all that's just Go code. But what about special gccgo files, like in x/sys/unix for syscalls, or all the Go assembly files which cannot be built on gccgo, like in x/crypto ?
CC @bradfitz @ianlancetaylor
The text was updated successfully, but these errors were encountered: