rust
biscuit
rust | biscuit | |
---|---|---|
5 | 12 | |
5 | 2,406 | |
- | 1.5% | |
0.0 | 0.0 | |
5 days ago | over 1 year ago | |
Rust | Go | |
GNU General Public License v3.0 or later | BSD 3-clause "New" or "Revised" License |
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.
biscuit
-
Biscuit 3.0
No, it isn't the third release of a POSIX like OS research written in Go,
https://github.com/mit-pdos/biscuit
-
If I know neither Go or Rust, which do I choose to learn first/only?
But there are other brave people exists like biscuit or gopher-os who can do it :)))
-
Pre-Overengineering
That's something I found in doing a bit of a dive on why ripgrep is so fast at doing a very specific kind of string search workload (Gallant / burntsushi / author of ripgrep is an actual wizard and contributes to Rust's regex engines, for reference). I wrote tiny proof of concepts in a variety of languages, all in my same style -- and sometimes my Go variants were as fast as the equivalent Rust/C (even in release / -O3/2 (every once in a blue moon, O3 makes no diff or is a slight regression in some exec paths)). I eventually found something about benchmarks in a related area, leading to this: https://benhoyt.com/writings/count-words/#performance-results-and-learnings. Somebody on the Go sub even linked me to the Biscuit OS: https://pdos.csail.mit.edu/papers/biscuit.pdf, which, tidbit, has Jon Gjengset (Crust of Rust legend) in the contribs list (https://github.com/mit-pdos/biscuit).
-
What is a "CPU Biscuit"?
https://github.com/mit-pdos/biscuit maybe this
-
Rust: A Critical Retrospective
Go has been used to implement OS kernel code, e.g. in the Biscuit OS from MIT: https://github.com/mit-pdos/biscuit
Of course, the garbage collector did not exactly make it easier - but it's an interesting piece of software.
- Can Go be used for kernel development?
- GOLang in embedded systems
-
GOLang in embedded systems (1 physical threads)
https://github.com/mit-pdos/biscuit says 5% slowdown over C. Garbage collection is going to require some more RAM, generally <=2x though.
- Biscuit operating system written in Go
- The difference between Go and Rust
What are some alternatives?
jnode - Code for the JNode operating system
Cosmos - Cosmos is an operating system "construction kit". Build your own OS using managed languages such as C#, VB.NET, and more!
FreeRTOS-rust - Rust crate for FreeRTOS
regex-automata - A low level regular expression library that uses deterministic finite automata.
snapbox - Snapshot testing for CLIs
TinyGo - Go compiler for small places. Microcontrollers, WebAssembly (WASM/WASI), and command-line tools. Based on LLVM.
xargo - The sysroot manager that lets you build and customize `std`
Harbol - Harbol is a collection of data structures and miscellaneous libraries, similar in nature to C++'s Boost, STL, and GNOME's GLib; it is meant to be a smaller and more lightweight collection of data structures, code systems, and convenience software.
wg-cargo-std-aware - Repo for working on "std aware cargo"
gopher-os - A proof of concept OS kernel written in Go
miri - An interpreter for Rust's mid-level intermediate representation