Skip to content

Latest commit

 

History

History
78 lines (67 loc) · 2.41 KB

README.md

File metadata and controls

78 lines (67 loc) · 2.41 KB
Raw

NCC - Not a C Compiler

The name NCC stands for "Not a C Compiler", because the compiler is a work in progress and not fully compliant. At this stage, it should be considered a toy compiler and you should expect to run into bugs and missing features. That being said, it is still a useful tool for the development of UVM, and the goal is to gradually increase the level of C compliance of NCC over time.

Supported features:

  • Global variables
  • Global arrays, two-dimensional arrays
  • Integer arithmetic and bitwise operations
  • Signed and unsigned integers, stdint.h
  • Character strings and the char type
  • The bool type
  • Pointers and pointer arithmetic, bitwise operations
  • The ternary operator a? b:c
  • sizeof() operator
  • Functions and function calls
  • If/else statements
  • For loops, while loops, do-while loops
  • C preprocessor
    • #include
    • #define constants
    • #define(a,b,c) macros
    • #undef
    • #ifdef / #ifndef
  • Headers for UVM bindings
    • #include <uvm/syscalls.h>
    • #include <uvm/utils.h>

Not yet implemented (TODO):

  • Structs
  • Unions
  • Enums
  • Typedefs
  • The const qualifier
  • Float and double types
  • The switch statement
  • Local arrays variables
  • Array initializers
  • Pointers to local variables

Caveats:

  • At the moment malloc() / free() don't use a free list, they just leak memory
  • Some error messages are currently fairly weak
    • Line numbers are currently inaccurate because of the preprocessor. This is a known bug.

Usage

Compiling a C program:

cargo run <your_c_file.c>

By default, the compiled output is written to out.asm.

Running tests:

cargo test

To use the UVM bindings, you should include the uvm/syscalls.h header. There are example programs under the examples directory that show the kinds of things NCC is able to compile and how to use the UVM APIs. You can also consult the source code for the UVM headers in the include directory to see which standard library functions are currently available. Contributions welcome.

The Test Suite

There is a set of C source files under the tests directory. These are automatically compiled by NCC and executed by UVM when running cargo test. The tests use the assert() macro to check that the behavior of the compiler is as expected. The goal is to increase test coverage over time and gradually increase the level of C compliance of NCC.