||2 years ago|
|test||2 years ago|
|NOTICE||2 years ago|
|README.cosmo||2 years ago|
|README.md||2 years ago|
|alloc.c||2 years ago|
|as.c||2 years ago|
|asm.c||2 years ago|
|cast.c||2 years ago|
|chibicc.c||2 years ago|
|chibicc.h||2 years ago|
|chibicc.mk||2 years ago|
|codegen.c||2 years ago|
|dox1.c||2 years ago|
|dox2.c||2 years ago|
|file.c||2 years ago|
|file.h||2 years ago|
|fpclassify.c||2 years ago|
|hashmap.c||2 years ago|
|main.c||2 years ago|
|parse.c||2 years ago|
|preprocess.c||2 years ago|
|printast.c||2 years ago|
|strarray.c||2 years ago|
|tokenize.c||2 years ago|
|type.c||2 years ago|
|unicode.c||2 years ago|
chibicc: A Small C Compiler
(The old master has moved to historical/old branch. This is a new one uploaded in September 2020.)
chibicc is yet another small C compiler that implements most C11 features. Even though it still probably falls into the "toy compilers" category just like other small compilers do, chibicc can compile several real-world programs, including Git, SQLite and libpng, without making modifications to the compiled programs. Generated executables of these programs pass their corresponding test suites. So, chibicc actually supports a wide variety of C11 features and is able to compile hundreds of thousands of lines of real-world C code correctly.
chibicc is developed as the reference implementation for a book I'm currently writing about the C compiler and the low-level programming. The book covers the vast topic with an incremental approach; in the first chapter, readers will implement a "compiler" that accepts just a single number as a "language", which will then gain one feature at a time in each section of the book until the language that the compiler accepts matches what the C11 spec specifies. I took this incremental approach from the paper by Abdulaziz Ghuloum.
Each commit of this project corresponds to a section of the book. For this purpose, not only the final state of the project but each commit was carefully written with readability in mind. Readers should be able to learn how a C language feature can be implemented just by reading one or a few commits of this project. For example, this is how while, , ?:, and thread-local variable are implemented. If you have plenty of spare time, it might be fun to read it from the first commit.
If you like this project, please consider purchasing a copy of the book when it becomes available! 😀 I publish the source code here to give people early access to it, because I was planing to do that anyway with a permissive open-source license after publishing the book. If I don't charge for the source code, it doesn't make much sense to me to keep it private. I hope to publish the book in 2021.
I pronounce chibicc as chee bee cee cee. "chibi" means "mini" or "small" in Japanese. "cc" stands for C compiler.
Features that are often missing in a small compiler but supported by chibicc include (but not limited to):
- long double (x87 80-bit floting point numbers)
- Variable-length array
- Thread-local variable
- Atomic variable
- Common symbol
- Designated initializer
- L, u, U and u8 string literals
chibicc does not support digraphs, trigraphs, complex numbers, K&R-style function prototype, and inline assembly.
chibicc outputs a simple but nice error message when it finds an error in source code.
There's no optimization pass. chibicc emits terrible code which is probably twice or more slower than GCC's output. I have a plan to add an optimization pass once the frontend is done.
chibicc consists of the following stages:
Tokenize: A tokenizer takes a string as an input, breaks it into a list of tokens and returns them.
Preprocess: A preprocessor takes as an input a list of tokens and output a new list of macro-expanded tokens. It interprets preprocessor directives while expanding macros.
Parse: A recursive descendent parser constructs abstract syntax trees from the output of the preprocessor. It also adds a type to each AST node.
Codegen: A code generator emits an assembly text for given AST nodes.
When I find a bug in this compiler, I go back to the original commit that introduced the bug and rewrite the commit history as if there were no such bug from the beginning. This is an unusual way of fixing bugs, but as a a part of a book, it is important to keep every commit bug-free.
Thus, I do not take pull requests in this repo. You can send me a pull request if you find a bug, but it is very likely that I will read your patch and then apply that to my previous commits by rewriting history. I'll credit your name somewhere, but your changes will be rewritten by me before submitted to this repository.
Also, please assume that I will occasionally force-push my local repository to this public one to rewrite history. If you clone this project and make local commits on top of it, your changes will have to be rebased by hand when I force-push new commits.
About the Author
I'm Rui Ueyama. I'm the creator of 8cc, which is a hobby C compiler, and also the original creator of the current version of LLVM lld linker, which is a production-quality linker used by various operating systems and large-scale build systems.
tcc: A small C compiler written by Fabrice Bellard. I learned a lot from this compiler, but the design of tcc and chibicc are different. In particular, tcc is a one-pass compiler, while chibicc is a multi-pass one.