Hi Tianon,

> The main issue with getting it in essentially boils down to gccgo and
> upstream Go disagreeing on the GOARCH for mips64el (gccgo uses
> "mipsn64"[0]), which makes bootstrapping difficult.
>
> [0]: https://groups.google.com/d/topic/golang-nuts/waTy56I_KWQ/discussion


Are you saying that the patch is more complex than just
s/mipsn64/mips64el/ ? Or are you saying you do not want to maintain
such patch until upstream add an alias for mips64el ?

Thanks

Reply via email to