Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
This branch is 2 commits ahead, 545 commits behind rust-lang:master.

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

WIP libgccjit codegen backend for rust

github sponsor patreon

This is a GCC codegen for rustc, which means it can be loaded by the existing rustc frontend, but benefits from GCC: more architectures are supported and GCC's optimizations are used.

Despite its name, libgccjit can be used for ahead-of-time compilation, as is used here.


The primary goal of this project is to be able to compile Rust code on platforms unsupported by LLVM. A secondary goal is to check if using the gcc backend will provide any run-time speed improvement for the programs compiled using rustc.


This requires a patched libgccjit in order to work. The patches in this repostory need to be applied. (Those patches should work when applied on master, but in case it doesn't work, they are known to work when applied on 079c23cfe079f203d5df83fea8e92a60c7d7e878.) You can also use my fork of gcc which already includes these patches.

Put the path to your custom build of libgccjit in the file gcc_path.

$ git clone
$ cd rustc_codegen_gcc
$ ./ # download and patch sysroot src
$ ./ --release

To run the tests:

$ ./ # download and patch sysroot src and install hyperfine for benchmarking
$ ./ --release


$cg_gccjit_dir is the directory you cloned this repo into in the following instructions.


$ CHANNEL="release" $cg_gccjit_dir/ run

If you compiled cg_gccjit in debug mode (aka you didn't pass --release to ./ you should use CHANNEL="debug" instead or omit CHANNEL="release" completely.


You should prefer using the Cargo method.

$ rustc +$(cat $cg_gccjit_dir/rust-toolchain) -Cpanic=abort -Zcodegen-backend=$cg_gccjit_dir/target/release/ --sysroot $cg_gccjit_dir/build_sysroot/sysroot

Env vars

Don't cache object files in the incremental cache. Useful during development of cg_gccjit to make it possible to use incremental mode for all analyses performed by rustc without caching object files when their content should have been changed by a change to cg_gccjit.
Display the time it took to perform codegen for a crate


Sometimes, libgccjit will crash and output an error like this:

during RTL pass: expand error: in expmed_mode_index, at expmed.h:249
0x7f0da2e61a35 expmed_mode_index
0x7f0da2e61aa4 expmed_op_cost_ptr
0x7f0da2e620dc sdiv_cost_ptr
0x7f0da2e62129 sdiv_cost
0x7f0da2e73c12 expand_divmod(int, tree_code, machine_mode, rtx_def*, rtx_def*, rtx_def*, int)
0x7f0da2ea1423 expand_expr_real_2(separate_ops*, rtx_def*, machine_mode, expand_modifier)
0x7f0da2cd1a1e expand_gimple_stmt_1
0x7f0da2cd1c30 expand_gimple_stmt
0x7f0da2cd90a9 expand_gimple_basic_block
0x7f0da2cdade8 execute

To see the code which causes this error, call the following function:

gcc_jit_context_dump_to_file(ctxt, "/tmp/output.c", 1 /* update_locations */)

This will create a C-like file and add the locations into the IR pointing to this C file. Then, rerun the program and it will output the location in the second line: /tmp/something.c:61322:0: error: in expmed_mode_index, at expmed.h:249

Or add a breakpoint to add_error in gdb and print the line number using:

p loc->m_line

How to use a custom-build rustc

  • Build the stage2 compiler (rustup toolchain link debug-current build/x86_64-unknown-linux-gnu/stage2).
  • Clean and rebuild the codegen with debug-current in the file rust-toolchain.


libgccjit AOT codegen for rustc






No releases published


No packages published