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

gccgo, doc: comments on doc/install/gccgo for gcc release 6 #14117

laboger opened this issue Jan 27, 2016 · 1 comment


Copy link

commented Jan 27, 2016

I know that it is likely that some changes are planned for for the release of gcc 6. Here are a few comments/suggestions on this page.

With the changes to split stack support in gccgo for gcc release 6, it no longer required to use --with-ld on the configure option (and probably better not to? maybe both methods should be described). In gcc 6, if the gold linker is found in the PATH when gcc is configured, then it will be used as the linker for gccgo, as required for split stack.

Also, split stack is now implemented for PowerPC64 big and little endian in addition to x86.

On the section describing how to build gccgo, another way to get gcc source is from the weekly snapshots or releases from the various mirrors for GNU GCC found here This is much faster than using svn to get the source.

When describing the setting of the LD_LIBRARY_PATH, the paths used are not correct based on the systems I've looked at (ppc64le & x86). The shared libraries are found under ${prefix}/lib64 or ${prefix}/lib, so that is the path needed for LD_LIBRARY_PATH or when setting the runpath with the -W option.

The example showing -gccgoflags should have the options within quotes.

It would be nice to see something that mentions the use of the go tool built for gccgo and how it is preferred over using gccgo directly or the go tool from golang with the -compiler option. When using the go tool built for gccgo, then using 'go version' displays version information about gccgo. Also, if 'go build' is used to build an application with build tags then it matches against the tags for gccgo as expected. When using the go tool from golang with the -compiler option, the build tags are matched against the golang values and not the gccgo values.

@ianlancetaylor ianlancetaylor added this to the Gccgo milestone Jan 27, 2016


This comment has been minimized.

Copy link

commented Jan 27, 2016

Thanks. Want to send in a change?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.