cargo-gccrs
gccrs
cargo-gccrs | gccrs | |
---|---|---|
5 | 102 | |
22 | 2,277 | |
- | 1.4% | |
1.6 | 10.0 | |
11 months ago | 1 day ago | |
Rust | ||
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
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.
cargo-gccrs
-
Rust Support Is Being Built into the GNU GCC Compiler
We have `cargo-gccrs` for this, so a cargo subcommand which intercepts arguments given to `rustc` and converts them into `gccrs` arguments :)
https://github.com/rust-GCC/cargo-gccrs/
it's still in a relatively early stage as we are focusing on the compiler. But the idea is for it to be a drop-in replacement for compilation and execution operations, so you'd have `cargo gccrs build`, `cargo gccrs run`, `cargo gccrs test`, etc
-
GCC gets a new frontend for Rust
gccrs is the compiler (like rustc). You can use cargo with gccrs : https://github.com/Rust-GCC/cargo-gccrs
-
GCC Rust front-end approved by GCC Steering Committee
See https://github.com/Rust-GCC/cargo-gccrs. There will definetly some sort of cargo support in the end. Either by having a behave-like-rustc wrapper around gccrs or by adding support directly to cargo or a cargo fork.
-
GCC Rust Approved by GCC Steering Committee
Cargo support for gccrs is part of this project:
https://github.com/Rust-GCC/cargo-gccrs
Moreover, modules are less interesting to me in embedded development as is access to Rust's borrow checker for gaining certainty of small portions of larger projects, which are written in other languages.
-
GCC Rust in 2021
- With the [cargo-gccrs](https://github.com/Rust-GCC/cargo-gccrs/) we want to integrate gccrs as seamless as possible into the Rust ecosystem. So yes.
gccrs
-
FreeBSD evaluating Rust's adoption into base system
There is a Rust front-end for GCC that is under active development [1]. If the chip vendors are not willing to develop and upstream a LLVM back-end then they can feel free to start contributing to it.
[1] https://rust-gcc.github.io/
-
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).
- Rust-GCC: GCC Front-End for Rust
-
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.
-
How hard is it to write a front end for a more complex language like Rust or Kotlin?
I recommend checking out the GCC Rust frontend project.
-
Rust contributions for Linux 6.4 are finally merged upstream!
That is what theyre refering to, yes. The GitHub is named https://github.com/Rust-GCC/gccrs
-
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.
- Break rust Easter Egg Merged Into gccrs
-
Any alternate Rust compilers?
(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.)
-
Which programming languages, if all legacy code written in them was ported to a more modern language, would become extinct?
That bridge will be crossed with gccrs (compiling Rust with gcc directly, coming next month with GCC 13) and rust_codegen_gcc (rustc frontend, GCC backend, works now but just doesn’t yet have an “easy” setup)
What are some alternatives?
rustc_codegen_gcc - libgccjit AOT codegen for rustc
gcc-rust - a (WIP) Rust frontend for gcc / a gcc backend for rustc
simh - The Computer History Simulation Project
hubris - A lightweight, memory-protected, message-passing kernel for deeply embedded systems.
rustc_codegen_gcc - libgccjit AOT codegen for rustc
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.
mold - Mold: A Modern Linker 🦠
miri - An interpreter for Rust's mid-level intermediate representation
rust - Empowering everyone to build reliable and efficient software.
llvm-project - The LLVM Project is a collection of modular and reusable compiler and toolchain technologies. This fork is used to manage Apple’s stable releases of Clang as well as support the Swift project.