Skip to content
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

x/all: gccgo support #31436

Helflym opened this issue Apr 12, 2019 · 2 comments


Copy link

commented Apr 12, 2019

In #31382, @mikioh asks an interesting questions about the maintenance of packages on gccgo.

How are we sure that the changes made in 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

@gopherbot gopherbot modified the milestones: Unreleased, Gccgo Apr 12, 2019


This comment has been minimized.

Copy link

commented Apr 12, 2019

CC @thanm


This comment has been minimized.

Copy link

commented Apr 12, 2019

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
None yet
4 participants
You can’t perform that action at this time.