rustc_codegen_gcc: Progress Report #36 (blog.antoyo.xyz)

submitted 5 days ago by antoyo@programming.dev to c/rust@programming.dev

7 comments fedilink hide all child comments

We've got a few bugs fixed that allowed us to fully bootstrap the Rust compiler with rustc_codegen_gcc and to fix the CI for Rust for Linux compiled with rustc_codegen_gcc. We hope to improve our testing within the Rust repo in order to allow us to move faster towards our goals.

you are viewing a single comment's thread
view the rest of the comments

[-] antoyo@programming.dev 4 points 4 days ago

Oh, sorry for the confusion: this is about rustc_codegen_gcc which is a codegen plugin for rustc that uses libgccjit to generate the object files via GCC instead of LLVM, so it still requires rustc. There's another project that is a GCC frontend, called gccrs. Also, bootstrap is overloaded: in this case, a full bootstrap means that we can compile the Rust compiler with rustc_codegen_gcc, producing a stage-2 compiler, then recompile the Rust compiler with this stage-2 compiler to get a stage-3 compiler and those 2 compares as equal.

[-] arendjr@programming.dev 3 points 4 days ago

That’s still a very major achievement! Do I understand correctly this means all target architectures supported by GCC are now unlocked for Rust too?

[-] antoyo@programming.dev 2 points 4 days ago

Well, we can generate code for targets not supported by LLVM, but it is not trivial to setup (we hope to get rustup support in the coming months to make this easier) and most GCC targets won't pass as many tests as x86-64 with rustc_codegen_gcc. There's some info in the wiki about some targets that people tried.

It is an optional goal for the Google Summer of Code to bootstrap the rust compiler on other platforms, so we might be able to get a working rustc for new platforms by the end of the summer.