-
Notifications
You must be signed in to change notification settings - Fork 55
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
Upstream RISC-V changes to allow for a Rust-lang port #30
Comments
I've been working on a local copy of rustc-nightly to try and get rust code to work. Even after adding target files for riscv64 (I haven't attempted a 32 bit target) and merging the differences between rust-llvm and riscv-llvm, the process to get it to build was very convoluted. I have just now been able to compile an empty rust library for riscv without stdcore and I still got error messages from llvm about:
though that is probably just an incorrect config file. The big problem that I have run into when trying to compile something a little bigger (define 2 variables and set one to the other), LLVM complained:
That was after compiling to llvm-ir and running llc, compiling rust to assembly directly emitted a much smaller error message for the same problem. [EDIT] Code block failure resulting in "referencing" every issue and pull request by accident. |
Quick update: the compiler segfaulted. The target that failed is
GDB says it was on line 46 of the llvm/lib/MC/MCELFStreamer.cpp. The odd thing about this is that it's using the llvm I pointed to with --llvm-root and is targeting risc-v. The backtrace of the core dump is here |
Any update on this effort? |
This particular RISC-V port is unlikely to be upstreamed because @asb has started upstreaming a different patch series. |
Needs to be updated with lowRISC/riscv-llvm? |
I just opened a ticket on the Rust-lang repository regarding a RISC-V port and was informed that we need to upstream the changes in this repository in order to be able to compile Rust without any issues.
Please let me know if and when this can be done. Thank you!
The text was updated successfully, but these errors were encountered: