How hard would it be to port the Rust toolchain to a new non-POSIX OS written in Rust and get it to host its own development? What would that process entail?

1. rust

   1 2,777 100,462 10.0 Rust

   Empowering everyone to build reliable and efficient software.

   

   A. Add your os to the ones under the sys folder and implement the needed types. The types here are internal os-specific versions of exposed std types. (you can go off of the implementations for the other oses and the documentation exposed type)

2. SaaSHub

   www.saashub.com featured

   SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

   

3. gccrs

   2 104 2,506 9.8 C++

   GCC Front-End for Rust

   

   There's ongoing work on a Rust front-end for GCC (https://github.com/Rust-GCC/gccrs). Bit barebones right now -- ie, even core doesn't compile -- but there's funding, demand, and regular progress, so it'll only get better from there. Once gccrs can compile core, it should be ready to compile most of Rust, and thus if you've taught the calling conventions for C to GCC, you're golden.

4. rustc_codegen_gcc

   3 50 941 9.3 Rust

   libgccjit AOT codegen for rustc

   

   Alternatively, there's another initiative called codegen_gcc which is about using GCC as a backend for the rustc compiler. It's (much) more advanced in Rust support, but I am not sure how easy it would be to use a modified libgccjit from there.

Suggest a related project