Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cranelift: loongarch64 support #9612

Open
k0tran opened this issue Nov 15, 2024 · 2 comments
Open

Cranelift: loongarch64 support #9612

k0tran opened this issue Nov 15, 2024 · 2 comments
Labels
cranelift:new-target Issues requesting Cranelift support for new targets.

Comments

@k0tran
Copy link

k0tran commented Nov 15, 2024

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?

@cfallin cfallin added the cranelift:new-target Issues requesting Cranelift support for new targets. label Nov 15, 2024
@cfallin
Copy link
Member

cfallin commented Nov 15, 2024

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.

@k0tran
Copy link
Author

k0tran commented Nov 15, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cranelift:new-target Issues requesting Cranelift support for new targets.
Projects
None yet
Development

No branches or pull requests

2 participants