Closed zunley closed 2 years ago
It looks like the decision is GOARCH=loong64
, see https://github.com/golang/go/issues/46229#issuecomment-861154674 The GOARCH
value was added to golang/go
in https://github.com/golang/go/commit/2b00a54baf2b677b2aaddd93c25b11ea4642a86f already.
@merore could you please update the PR to use GOARCH=loong64
and also add the corresponding build tags for backwards compatibility? Then we should be good to merge. Thanks!
Currently the kernel and libc ABIs are not upstream yet, thus subject to possible changes. The early version I saw was heavily MIPS-based, so has very little chance to be merged as-is; and this PR contains values from that era, I think. So maybe this PR should wait until the ABIs are sufficiently settled?
Thanks for the context @xen0n! I agree, in that case let's wait until the ABIs in kernel and libc are stable.
I run
go build . && ./mksysconf
generate zsysconf_values for linux_loongarch64.Currently golang of loongarch64 is waiting for the community to receive. All these values meets the definition in golang.org/x/sys/unix.
I open this PR because gopsutil needs. I don’t know if this approach is reasonable, please contact me if you have other suggestions.