-
Notifications
You must be signed in to change notification settings - Fork 37
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
Merge into main branch rust-lang/rust? #89
Comments
I don't think this can be done until the Xtensa backend is merged into upstream LLVM, but I could be wrong. |
@mcilloni is correct, Rust won't accept Xtensa support upstream without atleast an experimental backend in LLVM upstream. With the riscv chips, we've already upstreamed everything we can. |
Where to check the status? URLs that I'm missing:
|
espressif/llvm-project#4 implies that all of the repo's changes have been merged to upstream LLVM, although the PR hasn't been closed yet. What are the next steps? |
We have indeed got the first patch set merged into LLVM, however that set of patches is not yet sufficient for a working Rust compiler. |
Hey guys, just wanted to ping this as it seems there is some new traction over at the tracking issue espressif/llvm-project#4 seems this might be coming pretty close |
My understanding (somebody can correct me if I'm wrong) is that there are still a large number of patches which need to be merged into LLVM before full Xtensa support is realized. Once this is complete, it will take time for these changes to propagate into Rust as well. |
By now developers have to compile whole custom Rust toolchain to work with xtensa isa. Is there any possibility to merge xtensa instruction set support into main branch Rust? Then developers can install them easily by using rustup toolchain add command.
The text was updated successfully, but these errors were encountered: