David Daney <dda...@caviumnetworks.com> writes: > That's right, but for the sake of argument I would say that o64 is > unimportant as it is not supported by the Linux kernel.
It's unimportant but I'd like to make sure the scheme leaves room for it. >> It again comes down to what GOARCH is supposed to mean: an ABI, or what >> else? >> > > I would say it is only useful to distinguish the various ABIs. That > is the only thing any program really sees. I agree. > Since libgo doesn't even currently build under linux-mips*, we could > change the values of GOARCH generated for mips without causing > regressions. > > I would suggest: > > GOARCH=mips # o32 > GOARCH=mips64n32 # Would you believe n32? > GOARCH=mips64n64 # ...n64 I think the only real question is whether that first "64" helps. Perhaps we should just use mipso32, mipsn32, and mipsn64? Or should we just use mips instead of mipso32? Ian
