On 24/08/17 19:11, Shengjing Zhu wrote: > Control: severity -1 normal > > On Thu, Aug 24, 2017 at 10:37 PM, Martín Ferrari <[email protected]> wrote: >> Yes, sorry, I was confused with x/tools, which has disabled tests. This >> one does not get built in other arches, so the relevant tests are not >> executed.. Maybe we should make it arch:any...?
> I think the CI like ci.d.n should run on more archs instead... Yeah, that'd be ideal :) > ok, so I read the issue on https://github.com/golang/go/issues/18031 > > I don't have mips env to verify comments by foka. But what foka said > in that issue is, > gccgo reports mipsel and mips both as `mipso32`. So we need pass > another `-tags` to distinguish the two archs. > Unless gccgo has corrent build tip, we can only manually add `-tags > mips` or `-tags mipsel`. I have just tested that, with eller for mips(64)el and minkus for mips. And sadly, that is true: eller (mipsel): $ go env GOARCH="mipso32" eller (mips64el): $ go env GOARCH="mipsn64" minkus (mips): $ go env GOARCH="mipso32" The bug referenced above says this might be already fixed in gccgo, and looking at the commit history, it does seem to be true: https://go.googlesource.com/gofrontend/+/3f713ddb2a9a2a736f3a12d71c56cb7fd444afba%5E%21/ This harmonizes the arch names with gc, and as a side effect, fixes the missing little-endian marker. The problem is that gcc and friends make my head hurt, and I don't really understand if this made it into the 7.2 release or not. Seeing that eller has libgo 7.2, I assume it did not.. Does anybody understand all this? > BTW, let me down grade this bug's severity first since I think we have > workaround for that :) OK. -- Martín Ferrari (Tincho) _______________________________________________ Pkg-go-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
