Add target page for riscv64gc-unknown-linux-gnu #127490
Conversation
|
rustbot has assigned @GuillaumeGomez. Use |
rustbot
added
the
S-waiting-on-review
|
Some changes occurred in src/doc/rustc/src/platform-support cc @Nilstrieb |
Hoverbear
force-pushed
the
hoverbear/add-riscv64gc-unknown-linux-target-page
branch
from
ab4840b
to
32efd23
Compare
This comment has been minimized.
This comment has been minimized.
|
r? @Nilstrieb |
|
|
||
| This target requires: | ||
|
|
||
| * Linux Kernel version 4.20 or later |
There was a problem hiding this comment.
We may need to raise this to 6.6 given #117022 (comment)
There was a problem hiding this comment.
I'd leave that decision outside of a purely documentation PR.
|
|
||
| ## Target maintainers | ||
|
|
||
| - TODO |
There was a problem hiding this comment.
I see rust-embedded specifies some people that are part of the RISC-V team. I am not sure if this is the same as the target maintainers. If not, maybe they would know who this should be.
CC: @almindor @dkhayes117 @romancardenas @MabezDev @jessebraham
There was a problem hiding this comment.
riscv is a generic group, for me for example, while I'm happy to look at PRs, 64bit risc is something I cannot test since I currently do not own such hardware. Same goes for -linux targets, I only have bare-metal 32bit MCUs.
There was a problem hiding this comment.
Hi folks. As discussed separately with @Hoverbear, I am happy to help. @Hoverbear: Please let me know if there is anything else needed from me. Also note that there are at least 2 more colleagues who will shortly chime in in this thread who have agreed to be a part of this maintainers group. Thanks!
There was a problem hiding this comment.
Please feel free to include me as part of this maintainers group :)
There was a problem hiding this comment.
Count me in here, as a long-time RISC-V toolchain contributor, I am happy to help triage and resolve toolchain compiler issue for RISC-V :)
This comment has been minimized.
This comment has been minimized.
Hoverbear
force-pushed
the
hoverbear/add-riscv64gc-unknown-linux-target-page
branch
from
904351a
to
462a48e
Compare
|
r? @pietroalbini |
bors
added
S-waiting-on-bors
…unknown-linux-target-page, r=pietroalbini Add target page for riscv64gc-unknown-linux-gnu I was reading rust-lang#113739 and realized I knew most of the information necessary to create the `riscv64gc-unknown-linux-gnu` target page.
…iaskrgr Rollup of 6 pull requests Successful merges: - rust-lang#127490 (Add target page for riscv64gc-unknown-linux-gnu) - rust-lang#128433 (fix(hermit): `deny(unsafe_op_in_unsafe_fn)`) - rust-lang#128482 (interpret: on a signed deref check, mention the right pointer in the error) - rust-lang#128496 (Fix removed `box_syntax` diagnostic if source isn't available) - rust-lang#128497 (fix dropck documentation for `[T;0]` special-case) - rust-lang#128499 (chore: refactor backtrace formatting) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#127490 - ferrocene:hoverbear/add-riscv64gc-unknown-linux-target-page, r=pietroalbini Add target page for riscv64gc-unknown-linux-gnu I was reading rust-lang#113739 and realized I knew most of the information necessary to create the `riscv64gc-unknown-linux-gnu` target page.
pietroalbini
deleted the
hoverbear/add-riscv64gc-unknown-linux-target-page
branch
I was reading #113739 and realized I knew most of the information necessary to create the
riscv64gc-unknown-linux-gnutarget page.