rustc_codegen_gcc
Rust-for-Linux
Our great sponsors
rustc_codegen_gcc | Rust-for-Linux | |
---|---|---|
33 | 79 | |
9 | 3,769 | |
- | 1.9% | |
9.7 | 0.0 | |
4 days ago | 4 days ago | |
Rust | C | |
Apache License 2.0 | 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.
rustc_codegen_gcc
- Rust Support in the Linux Kernel
-
GCC Rust Monthly Report #9 August 2021
It's true that if this project succeeds, that would be an outcome, but it's probably worth noting that you'd really only have to add support for the GCC backend to do that, and not reimplement the frontend as well (parsing, type checking, lifetime checking, etc.). There's an unrelated project working to do that: https://github.com/antoyo/rustc_codegen_gcc that would likely yield those same benefits for less effort.
-
Recursive fib is faster in C++?
Here's the gcc backend for rustc here https://github.com/antoyo/rustc_codegen_gcc Since this just swaps the optimizer/codegen module and reuses all the other stuff from rustc it needs less work and can already compile many valid rust programs.
-
Anyone used the gcc backend before?
I'd like to use the rustc_codegen_gcc backend to compile some Rust programs, but I'm confused about how to install and use the patched libgccjit dependency. I've downloaded the fork provided but don't know where to go from there.
-
The Tor Project announces Arti, a Tor implementation written in Rust from scratch
I was being a little sloppy and mixing together "actual embedded hardware" with "extensions for applications written in other languages" in my head. I think your point about LLVM is still accurate, though I hear peeps about different projects working on GCC support from time to time.
-
Rust GCC back end was officially accepted into the compiler
This doesn't have anything to do with using GCC to compile rust, but instead using rustc to compile Rust using the GCC backend. You can do that today by using the linked project, rustc_codegen_gcc, which is intended to be integrated into rustc at some point in the (hopefully near) future.
-
This is the patch series to add support for Rust as a second language to the Linux kernel.
Rather than mrustc you should probably look at rustc_codegen_gcc which uses gcc as a backend to rustc (WIP) or GCC Rust which tries to implement a rust frontend for gcc (also WIP). I think rustc_codegen_gcc looks the most promising at the moment
-
Hacker News top posts: Jul 6, 2021
Libgccjit AOT Codegen for Rustc\ (2 comments)
- Libgccjit AOT Codegen for Rustc
-
GCC Rust Monthly Report #6 May 2021
It is impressive work but I still think that using libgccjit as a backend is the right way forward since once it has been integrated it should be much less work to maintain.
Rust-for-Linux
-
The Linux Kernel Prepares for Rust 1.77 Upgrade
At least according to the Github's language breakdown for https://github.com/Rust-for-Linux/linux, C is still 98.3% of the repository, and Rust is in the 0.1% of "others".
Rust is backwards compatible when you stick to stable features, but the kernel uses unstable features that can and do incur breaking changes.
-
Mark Russinovich: “Working towards enabling Windows driver development in Rust”
> How would this work?
Don't know exactly what you're asking.
> And why would it be a better idea?
Poorly written device drivers are a significant attack vector. It's one of the reasons Linux is now exploring using Rust for its own device drivers.[0] You may be asking -- why Rust and not some other language? Rust has many of the performance and interoperability advantages of C and C++, but as noted, makes certain classes of memory safety issues impossible. Rust also has significant mindshare among systems programming communities.
-
The Linux Kernel Module Programming Guide
Ctrl-F "rust"
https://rust-for-linux.com/ links to LWN articles at https://lwn.net/Kernel/Index/#Development_tools-Rust that suggest that only basic modules are yet possible with the rust support in Linux kernels 6.2 and 6.3.
Rust-for-linux links to the Android binder module though:
> Android Binder Driver: This project is an effort to rewrite Android's Binder kernel driver in Rust.
> Motivation: Binder is one of the most security and performance critical components of Android. Android isolates apps from each other and the system by assigning each app a unique user ID (UID). This is called "application sandboxing", and is a fundamental tenet of the Android Platform Security Model.
> The majority of inter-process communication (IPC) on Android goes through Binder. Thus, memory unsafety vulnerabilities are especially critical when they happen in the Binder driver
... "Rust in the Linux kernel" (2021) https://security.googleblog.com/2021/04/rust-in-linux-kernel... :
> [...] We also need designs that allow code in the two languages to interact with each other: we're particularly interested in safe, zero-cost abstractions that allow Rust code to use kernel functionality written in C, and how to implement functionality in idiomatic Rust that can be called seamlessly from the C portions of the kernel.
> Since Rust is a new language for the kernel, we also have the opportunity to enforce best practices in terms of documentation and uniformity. For example, we have specific machine-checked requirements around the usage of unsafe code: for every unsafe function, the developer must document the requirements that need to be satisfied by callers to ensure that its usage is safe; additionally, for every call to unsafe functions (or usage of unsafe constructs like dereferencing a raw pointer), the developer must document the justification for why it is safe to do so.
> We'll now show how such a driver would be implemented in Rust, contrasting it with a C implementation. [...]
This guide with unsafe rust that calls into the C, and then with next gen much safer rust right next to it would be a helpful resource too.
What of the post-docker container support (with userspaces also written in go) should be cloned to rust first?
-
The state of Flatpak security: major Projects are the worst?
Rust-for-Linux issue tracker
- rust devs in a nutshell
-
Rustproofing Linux (Part 1/4 Leaking Addresses)
Also, there already exists both issue: https://github.com/Rust-for-Linux/linux/issues/479
Yes, I definitely agree that it's a problem that pr_info implicitly wraps its arguments in unsafe {}. I wrote my own Pull Request with a trival fix.
-
how to compile a rust "hello world" with kernel 6.1?
Note that this template won't work with Linux 6.1, which has very minimal Rust support. You'll want the RustForLinux tree, or maybe Linux 6.2.
-
Rust in the 6.2 Kernel
> Also we’re bringing NPM style supply chain problems to the kernel now?
Nope. They've thought that through.
(In fact, cargo is only used to build test helpers. https://github.com/Rust-for-Linux/linux/blob/rust/Documentat...)
What are some alternatives?
gccrs - GCC Front-End for Rust
jakt - The Jakt Programming Language
rfcs - RFCs for changes to Rust
dafny - Dafny is a verification-aware programming language
rustig - A tool to detect code paths leading to Rust's panic handler
koka - Koka language compiler and interpreter
PrawnOS - Libre Mainline Kernel and Debian for arm laptops
btleplug - Rust Cross-Platform Host-Side Bluetooth LE Access Library
polonius - Defines the Rust borrow checker.
no-panic - Attribute macro to require that the compiler prove a function can't ever panic
avr-hal - embedded-hal abstractions for AVR microcontrollers