gccrs
rustc_codegen_cranelift
Our great sponsors
gccrs | rustc_codegen_cranelift | |
---|---|---|
102 | 44 | |
2,246 | 1,404 | |
2.7% | 5.6% | |
9.9 | 9.7 | |
4 days ago | 7 days ago | |
Rust | ||
GNU General Public License v3.0 only | 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.
gccrs
-
Why do lifetimes need to be leaky?
That's why gccrs doesn't even consider lifetime checking a part of the language (they plan to use Polonius, too).
-
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?
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.
-
Rust contributions for Linux 6.4 are finally merged upstream!
Do you mean this project https://rust-gcc.github.io/ ?
That is what theyre refering to, yes. The GitHub is named https://github.com/Rust-GCC/gccrs
Unsure currently, but there is project to get gcc to compile rust directly https://rust-gcc.github.io/ that is working to get changes upstreamed.
-
GCC 13 and the State of Gccrs
- But this misses so much extra context information
3. Macro invocations there are really subtle rules on how you treat macro invocations such as this which is not documented at all https://github.com/Rust-GCC/gccrs/blob/master/gcc/rust/expan...
Some day I personally want to write a blog post about how complicated and under spec'd Rust is, then write one about the stuff i do like it such as iterators being part of libcore so i don't need reactive extensions.
-
Any alternate Rust compilers?
Another upcoming implementation is Rust-GCC. This may help with wider adoption of Rust programs, but it probably won't see much use or support by Rust users. Furthermore, it will probably take some time to be implemented, since writing a compiler frontend is a difficult task.
In the future: gccrs (https://github.com/Rust-GCC/gccrs) is making progress, but is not useful now. It will be the first alternative compiler for Rust if/when complete (it probably will be completed because of the whole Rust for Linux effort)
(Speaking of which, Rust-GCC (or gcc-rs or gccrs or whichever other of their names they decide is the primary one) isn't even going to be a complete C++ implementation. Their plan is to implement enough to compile Polonius (the NLL 2.0 borrow checker being developed in Rust for rustc) and then share that since borrow-checking isn't necessary for codegen... only to identify and reject invalid programs... making the C++ portion of it not that different in scope from mrustc.)
-
why GNU grep is fast
If it were proposed, it may end up being a political issue. GNU wants things under their umbrella to be GNU GPL licensed, and the rust compiler is not. There is work to get a Rust compiler built into gcc, but it's not nearly ready yet.
rustc_codegen_cranelift
-
Cranelift code generation comes to Rust
Windows is supported. See https://github.com/rust-lang/rustc_codegen_cranelift/issues/....
-
A Guide to Undefined Behavior in C and C++
> When this happens, it seems like it'll be possible to get the LLVM bits out of the bootstrap process and lead to a fully self-hosted Rust.
What do you mean by "when this happens"? GP's point is that this has already happened: the Cranelift backend is feature-complete from the perspective of the language [0], except for inline assembly and unwinding on panic. It was merged into the upstream compiler in 2020 [1], and a compiler built with only the Cranelift backend is perfectly capable of building another compiler. LLVM hasn't been a necessary component of the Rust compiler for quite some time.
-
What are some stuff that Rust isn't good at?
Note that the Cranelift codegen will eventually become standard for debug builds to speed them up.
-
Rust port of B3 from WebKit, LLVM-like backend
Maybe one day we'll have rustc b3 backend like what they did with Cranelift
-
Any alternate Rust compilers?
Additionally, there is gcc codegen for rustc (https://github.com/rust-lang/rustc_codegen_gcc), which is not a compiler per se, but an alternative code generator, with more architectures supported and other nice things. It's also coming along, but there's still a lot of work to do there too. There's also Cranelift codegen (https://github.com/bjorn3/rustc_codegen_cranelift), which is designed to make debug builds faster, but this is not as exciting/useful as the other 2.
-
Capsules, reactive state, and HSR: Perseus v0.4.0 goes stable!
For the instant reloading, that's in Sycamore, so you should speak to its devs, but as for the alternative compiler backend, it's not my project, but it uses Cranelift and works pretty well! See https://github.com/bjorn3/rustc_codegen_cranelift for details.
- Security Engineer looking for ways to see if any of my tasks could slowly be ported to Rust or should I just stick with Python.
-
Improving Rust compile times to enable adoption of memory safety
Cranelift is not used for debug builds by default. I think that's probably a goal (although I'm not actually 100% sure about that just because I'm not dialed into what the compiler team is doing). Even the OP mentions this:
> We were able to benchmark bjorn3's cranelift codegen backend on full crates as well as on the build dependencies specifically (since they're also built for cargo check builds, and are always built without optimizations): there were no issues, and it performed impressively. It's well on its way to becoming a viable alternative to the LLVM backend for debug builds.
And the Cranelift codegen backend itself is also clear about it not being ready yet: https://github.com/bjorn3/rustc_codegen_cranelift
(To be clear, I am super excited about using Cranelift for debug builds. I just want to clarify that it isn't actually used by default yet.)
The more immediate goal of "distribute the cranelift backend as a rustup component" has been making good progress and seems like it might happen relatively soon https://github.com/bjorn3/rustc_codegen_cranelift/milestone/...
What are some alternatives?
gcc-rust - a (WIP) Rust frontend for gcc / a gcc backend for rustc
rustc_codegen_gcc - libgccjit AOT codegen for rustc
rustc_codegen_gcc - libgccjit AOT codegen for rustc
mold - Mold: A Modern Linker ðŸ¦
rust - Empowering everyone to build reliable and efficient software.
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.
polonius - Defines the Rust borrow checker.
mrustc - Alternative rust compiler (re-implementation)
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
wasmtime - A fast and secure runtime for WebAssembly
whisperfish
sccache - Sccache is a ccache-like tool. It is used as a compiler wrapper and avoids compilation when possible. Sccache has the capability to utilize caching in remote storage environments, including various cloud storage options, or alternatively, in local storage.