rust
wg-cargo-std-aware
| rust | wg-cargo-std-aware | |
|---|---|---|
| 5 | 4 | |
| 5 | 128 | |
| - | 0.0% | |
| 0.0 | 0.0 | |
| 2 days ago | about 3 years ago | |
| Rust | ||
| GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rust
-
[Help] How do I port Rust to a new OS where there is no LLVM support?
For what it's worth, this is the script I'm using to build for our platform: build.ps1 / build.sh
-
Can i create a rust compiler for my custom made OS?
Note that before I got the target triple upstream, I had to provide my own target json file. That's here: https://github.com/betrusted-io/rust/blob/1.53.0-xous/riscv32imac-unknown-xous-elf.json and you can adapt it as necessary. Simply creating the file in the correct path is enough. This is the code that does that: https://github.com/betrusted-io/rust/blob/e39344c5473d49a0cb4d45de119ad23713a00ed4/rebuild.ps1#L65
-
How to fully replace/reimplement std?
Everything you need to know to build for our platform is at https://github.com/betrusted-io/rust/ and maybe the scripts or patches there will be interesting to you.
-
Rust: A Critical Retrospective
Rust does use a Rust port of dlmalloc on platforms that don't provide malloc() and free(). We did port this to Xous, but ran into a feature bug that caused locking to be disabled. That was the source of weird and subtle bugs, which is how he discovered that fact about allocators.
This is correct.
When you tell someone to install Rust, they go to rustup.rs and install the latest version. Therefore, we need to have a libstd port for the latest version. Which effectively means we need to release libstd as soon as possible after the compiler is released. Our `sys` directory is at https://github.com/betrusted-io/rust/tree/1.61.0-xous/librar... and isn't too complicated. It's about 50 patches that need to be carried forward every six weeks.
Fortunately libstd doesn't change too much, at leaset not the parts we need. And I can usually pre-port the patches by applying them to `beta`, which means the patches against the release version usually apply cleanly.
It's still better than requiring nightly, which has absolutely no stability guarantees. By targeting stable, we don't run into issues of bitrot where we accidentally rely on features that have been removed. Rather than adjusting every service in the operating system, we just need to port one library: libstd
I've considered trying to upstream these, but I'm not sure how the rust team would feel about it.
wg-cargo-std-aware
- What are legitimate problems with Rust?
-
How to fully replace/reimplement std?
While it's planned, cargo doesn't support that right now (issues on this are tracked here: https://github.com/rust-lang/wg-cargo-std-aware).
-
Writing #![no_std] crates
When I created cargo-nono ~2.5 years ago, I honestly assumed that by now that tool would be cargo itself, which is one of the goals of the "std aware Cargo" WG.
-
ABI stability of rust_eh_personality?
Have you read https://github.com/rust-lang/wg-cargo-std-aware/issues/29 ?
What are some alternatives?
jnode - Code for the JNode operating system
actix-telepathy - Cluster extension for actix
FreeRTOS-rust - Rust crate for FreeRTOS
xargo - The sysroot manager that lets you build and customize `std`
snapbox - Snapshot testing for CLIs
async-fundamentals-initiative
rfcs - RFCs for changes to Rust
miri - An interpreter for Rust's mid-level intermediate representation
heapless - Heapless, `static` friendly data structures