rust
miri
rust | miri | |
---|---|---|
5 | 122 | |
5 | 3,973 | |
- | 2.7% | |
0.0 | 10.0 | |
5 days ago | 5 days ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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.
miri
-
Rust: Box Is a Unique Type
>While we are many missing language features away from this being the case, the noalias case is also magic descended upon box itself, with no user code ever having access to it.
I'm not sure why the author thinks there's magic behind Box. Box is not a special case of `noalias`. Run this snippet with miri and you'll see the same issue: https://play.rust-lang.org/?version=stable&mode=debug&editio...
`Box` _does_ have an expectation that its inner pointer is not aliased to another Box (even if used for readonly operations). See: https://github.com/rust-lang/miri/issues/1800#issuecomment-8...)
-
Bytecode VMs in Surprising Places
Miri [0] is an interpreter for the mid-level intermediate representation (MIR) generated by the Rust compiler. MIR is input for more processing steps of the compiler. However miri also runs MIR directly. This means miri is a VM. Of course it's not a bytecode VM, because MIR is not a bytecode AFAIK. I still think that miri is a interesting example.
And why does miri exist?
It is a lot slower. However it can check for some undefined behavior.
[0]: https://github.com/rust-lang/miri
-
RFC: Rust Has Provenance
Provenance is a dynamic property of pointer values. The actual underlying rules that a program must follow, even when using raw pointers and `unsafe`, are written in terms of provenance. Miri (https://github.com/rust-lang/miri) represents provenance as an actual value stored alongside each pointer's address, so it can check for violations of these rules.
Lifetimes are a static approximation of provenance. They are erased after being validated by the borrow checker, and do not exist in Miri or have any impact on what transformations the optimizer may perform. In other words, the provenance rules allow a superset of what the borrow checker allows.
- Mir: Strongly typed IR to implement fast and lightweight interpreters and JITs
-
Running rustc in a browser
There has been discussion of doing this with MIRI, which would be easier than all of rustc.
-
Piecemeal dropping of struct members causes UB? (Miri)
This issue has been fixed: https://github.com/rust-lang/miri/issues/2964
- Erroneous UB Error with Miri?
-
I've incidentally created one of the fastest bounded MPSC queue
Actually, I've done more advanced tests with MIRI (see https://github.com/rust-lang/miri/issues/2920 for example) which allowed me to fix some issues. I've also made the code compatible with loom, but I didn't found the time yet to write and execute loom tests. That's on the TODO-list, and I need to track it with an issue too.
-
Interested in "secure programming languages", both theory and practice but mostly practice, where do I start?
He is one of the big brains behind Miri, which is a interpreter that runs on the MIR (compiler representation between human code and asm/machine code) and detects undefined behavior. Super useful tool for language safety, pretty interesting on its own.
-
Formal verification for unsafe code?
I would also run your tests in Miri (https://github.com/rust-lang/miri) to try to cover more bases.
What are some alternatives?
jnode - Code for the JNode operating system
cons-list - Singly-linked list implementation in Rust
FreeRTOS-rust - Rust crate for FreeRTOS
sanitizers - AddressSanitizer, ThreadSanitizer, MemorySanitizer
snapbox - Snapshot testing for CLIs
rust - Empowering everyone to build reliable and efficient software.
xargo - The sysroot manager that lets you build and customize `std`
Rust-Full-Stack - Rust projects here are easy to use. There are blog posts for them also.
wg-cargo-std-aware - Repo for working on "std aware cargo"
rfcs - RFCs for changes to Rust
heapless - Heapless, `static` friendly data structures
nomicon - The Dark Arts of Advanced and Unsafe Rust Programming