Is RISC-V support "officially" still considered only experimental in 1.16+?

[neilschel...@gmail.com]

Hi Folks,

Apologies if this is clearly stated somewhere, but various searches didn't turn anything up.

We're trying to make a rudimentary first cut at risk assessment for using Go 1.16+ on RISC-V.  I see that 1.14 lists it as experimental but I don't see any subsequent "ready for prime time" announcement.

Likewise, is there any official-ish position on the future of support by the core team?

Regards,

Neil

[Ian Lance Taylor]

Joel, would it be reasonable to say that RISC-V is now fully supported
(albeit not a first-class port per
https://golang.org/wiki/PortingPolicy)? Anybody else have an opinion?
Thanks.

Ian

> --
> You received this message because you are subscribed to the Google Groups "golang-nuts" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/d2204d8d-870e-4566-8157-66adc34b3911n%40googlegroups.com.

[Joel Sing]

On 21-07-22 21:23:35, Ian Lance Taylor wrote:
> Joel, would it be reasonable to say that RISC-V is now fully supported
> (albeit not a first-class port per
> https://golang.org/wiki/PortingPolicy)? Anybody else have an opinion?

Apologies for the delayed response.

I'm not aware of any reason why it would not be considered as fully
supported.

I believe the (only?) reason it was marked as experimental in Go
1.14 was in case something needed to change significantly (such as
the assembly syntax) - the port itself was stable and has only
gained functionality and improved since then. The only assembly
related change that probably should have occurred is the inversion
of the register order for SUB (although that ship may have sailed
by now).

There are a handful of things that the port does not yet support
(c-shared, plugin, internal cgo linking, etc), but most of these
will not impact general usability.

On the other hand, there are various projects that depend on having
Go working on linux/riscv64, hence I would not expect it to become
unsupported any time soon (as an aside, there were at least four
different people who submitted changes/improvements to the port
during the current development cycle).

Hope this helps!