cherrymui
cherrymui
Hi @abner-chenc , Thanks for your contributions to the loong64 port! I've discussed this request with the team, and we agreed to grant you access. I've added you to the...
If it is only a test issue, and user's normal "go build" (be default, without any extra weird flags) is still reproducible, I think it is okay to just update...
Probably already fixed.
cc @golang/openbsd
This is actually a real bug. Thanks @S-YOU for reporting. I'll send a fix soon.
(I commented on the CL. Mention here for discussion) I agree that wasm_exec.js and perhaps wasm_exec_node.js are "runtime files" because they provide the necessary JS host support to run Go...
> for the js/wasm port no different than it is possible for other ports I don't think that's the case. Currently we don't provide an exec wrapper for any cross-compiled...
It seems most people think it helpful to include the exec wrappers. I think that is fine. One difference for the exec wrappers are that, unlike most things included in...
Go 1.21 will be out of support soon, certainly before Xcode 16 is released. So I don't think we need to do Go 1.21.
> however please create backport for 1.21 as well. As commented above https://github.com/golang/go/issues/68198#issuecomment-2191912515 I don't think we need to backport to Go 1.21. Could you explain why that is necessary?...