Stream: git-wasmtime

Topic: wasmtime / issue #9612 Cranelift: loongarch64 support

view this post on Zulip Wasmtime GitHub notifications bot (Nov 15 2024 at 07:43):

k0tran opened issue #9612:

Feature

loongarch64 is a cpu architecture. Right now Rust has loongarch64-unknown-linux-gnu and loongarch64-unknown-linux-musl targets thanks to LLVM. I wonder if its support is even planned in cranelift.

Benefit

loongarch64 is already supported by Rust compiler - most crates you can compile to loongarch64 on loongarch64. One of exceptions to this general rule is the Zellij. It depends on the cranelift-codegen internally.

Implementation

TODO: Do you have an implementation plan, and/or ideas for data structures or
algorithms to use?

Alternatives

TODO: What are the alternative implementation approaches or alternative ways to
solve the problem that this feature would solve? How do these alternatives
compare to this proposal?

view this post on Zulip Wasmtime GitHub notifications bot (Nov 15 2024 at 07:53):

cfallin added the cranelift:new-target label to Issue #9612.

view this post on Zulip Wasmtime GitHub notifications bot (Nov 15 2024 at 07:55):

cfallin commented on issue #9612:

Thanks for creating this issue! Are you interested in working on this?

I'll leave a link to this comment giving a high-level picture of the timelines and costs associated with new-target support. We're a fairly small team and a new backend is a large project, so the most likely way this would happen is if someone steps forward and volunteers to do the work, and then stick around as a maintainer afterward.

view this post on Zulip Wasmtime GitHub notifications bot (Nov 15 2024 at 09:20):

k0tran commented on issue #9612:

Thanks for creating this issue! Are you interested in working on this?

I'll leave a link to this comment giving a high-level picture of the timelines and costs associated with new-target support. We're a fairly small team and a new backend is a large project, so the most likely way this would happen is if someone steps forward and volunteers to do the work, and then stick around as a maintainer afterward.

Thanks, I see. I might try doing something. Although I'm pretty much sure that time requirements multiplied by my skill gap will result in too much time for porting one of terminal multiplexers (and creating cranelift backend in the process :D). But we'll see

Last updated: Nov 22 2024 at 16:03 UTC