-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Initial support for riscv32gc_unknown_linux_gnu #76048
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @matthewjasper (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
cc @rust-lang/compiler |
☔ The latest upstream changes (presumably #74862) made this pull request unmergeable. Please resolve the merge conflicts. |
Signed-off-by: Alistair Francis <[email protected]>
Signed-off-by: Alistair Francis <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello Alistair, good to see you again - this is the second RISCV PR I've reviewed 😄 https://gitlab.com/YottaDB/DB/YDB/-/merge_requests/777 oops, got that one mixed up with https://gitlab.com/YottaDB/DB/YDB/-/merge_requests/835
@alistair23 if you can resolve the conflicts, we can move this PR forward. Thanks :) |
4e63faf
to
82bd5a3
Compare
I have fixed the conflicts, I'm seeing some failures though. I'm assuming that's because we aren't using the latest glibc, but I can't figure out how to test that. |
i've created a zulip thread in case you need a place to ask help debugging the issue |
|
@rustbot ping risc-v |
Hey RISC-V Group! This bug has been identified as a good "RISC-V candidate". |
@alistair23 could you add a line describing the target to |
Signed-off-by: Alistair Francis <[email protected]>
Done! |
Signed-off-by: Alistair Francis <[email protected]>
@bors r+ |
📌 Commit e968f86 has been approved by |
Rollup of 10 pull requests Successful merges: - rust-lang#73955 (deny(unsafe_op_in_unsafe_fn) in libstd/process.rs) - rust-lang#75146 (Detect overflow in proc_macro_server subspan) - rust-lang#75304 (Note when a a move/borrow error is caused by a deref coercion) - rust-lang#75749 (Consolidate some duplicate code in the sys modules.) - rust-lang#75882 (Use translated variable for test string) - rust-lang#75886 (Test that bounds checks are elided for [..index] after .position()) - rust-lang#76048 (Initial support for riscv32gc_unknown_linux_gnu) - rust-lang#76198 (Make some Ordering methods const) - rust-lang#76689 (Upgrade to pulldown-cmark 0.8.0) - rust-lang#76763 (Update cargo) Failed merges: r? `@ghost`
Now that RISC-V 32-bit (RV32) support is in upstream glibc let's add support for userspace Rust.