On Tue, Feb 28, 2017 at 7:33 AM, James Cowgill <james.cowg...@imgtec.com> wrote: > > Stumbling over this thread: > https://groups.google.com/forum/#!topic/golang-nuts/waTy56I_KWQ > > On 25/03/16 17:08, Ian Lance Taylor wrote: >> mipsn64 is a GOARCH value used by gccgo, but not by gc. The gc >> compiler uses mips64 and mips64le. It's not clear to me how we are >> going to resolve this. > > This is still a problem. It is currently not possible to build golang > using gccgo on mips* due to it. What is the solution? Why can't (for > instance) gccgo move to using the GOARCH values from golang?
The complexity is that since gccgo is based on GCC, it supports multiple different calling conventions. Which calling convention should "mips64" represent? I don't have an answer. I also haven't really thought about it. Ian -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
