Note
We have reached a point where we are faced with higher obligations that somewhat set this project aside.
Therefore, from 8/5/25
to 9/6/25
, there will be a HIATUS in the development of the compiler and its plans moving forward.
Essentially, not much, just that thrushc
won't be reflected with commits regularly or habitually.
The other projects or repositories of the organization will continue with the planned development pace, but with a little less frequency.
If you'd like to be part of the team, please contact us through the organization's social media channels. They will continue as usual.
Without anything else to say, Kevin Benavides, see you next month.
Warning
The compiler is in an early development stage; it may contain bugs until a code fuzzer is developed for each backend code generator. Build it at your own risk.
The Thrush Compiler efficiently transfers source code from Thrush files directly to the intended target. Beyond this, it serves as a flexible bridge, integrating with diverse code generators for both research and development purposes.
Warning
While the compiler itself can theoretically generate code for these architectures, successful compilation into executable files (like .o files or final binaries) ultimately depends on your host system having the necessary toolchain components (e.g., assemblers, linkers, system libraries) for that specific target. The assembler should, however, produce output without issues.
Beyond the standard triple targets, the compiler also supports all architectures available through the LLVM-C API. These include:
x86_64
AArch64
RISC-V
ARM
MIPS
PowerPC
SystemZ
AMDGPU
Hexagon
Lanai
LoongArch
MSP430
NVPTX
SPARC
XCore
BPF
SPIR-V
WebAssembly
The GCC compiler backend is still under construction.
In the future, you will be able to use it with the -gcc
flag to use the GCC backend code generator instead of the default LLVM one.
However, it is only available on Linux.
You must also have libgccjit.so
dynamically installed in your distribution so that the compiler doesn't get scared at runtime when using GCC.
The language syntax is under construction at the same time as the compiler. It may be outdated compared to the compiler, as the latter progresses more rapidly. This will be normalized once a valid and sufficiently stable beta is released.
Thrush Programming Language - General Syntax
Currently, the only backend available for the thrush compiler to compile is the current LLVM, using the LLVM-C API.
The compiler has Clang compiled for Linux & Windows inside the executable in case the programmer does not have access to it; however, you can specify a custom Clang & GCC.
The code generation is in 3 phases.
- Intermediate Code Generation (
LLVM IR
). - Emit object files (
.o
). - Linking with some linker through the
Clang
orGCC
C compilers. ~ Rust 2015 be like
In summary:
You must first clone the repository and access it locally.
git clone --depth 1 https://github.com/thrushlang/thrushc && cd thrushc
Among the dependencies required by the compiler is the LLVM-C API, which you can find pre-compiled for each operating system at Thrush Programming Language Toolchains.
Automatically:
cd builder && cargo run
Now you need to have Rust installed with a recent version.
- >= Rust (v1.18.5)
- Rust 2024 Edition
Now you need to compile the compiler with Rust.
cargo run -- --help
Regarding the concept of bootstrapping in compilers (For more information: https://www.bootstrappable.org/).
The decision was made to fully implement all the programming language functions in the compiler written in Rust, because it proposes a development approach similar to what Gleam Team did for Gleam Programming Language, and also to lighten the workload, given that we are already using LLVM.