Skip to content

Akshat-Oke/Mini-C

Repository files navigation

Mini-C

A compiler for a subset of C, made using lex and yacc.

Language features

Before we get to the details, here is a program that can successfully run:

int factorial(int n)
{
  int a = 1;
  for (int i = 1; i <= n; i = i + 1)
  {
    a = a * i;
  }
  return a;
}
int main()
{
  int start = time(); //native function
  char str[] = "Factorial is %d\n"; //array passed to printf
  for (int i = 1; i < 20; i = i + 1) //there is no increment operator
  {
    printf(str, factorial(i)); //native printf
  }
  int end = time();
  int writtenChars = printf("Time taken: %d milliseconds\n", end - start);
  return writtenChars;
}

Looks good, except that factorial ends up returning negative values due to overflow. time() also returns negative (signed) values of the milliseconds since epoch, but the difference is correct. int can be printed as an unsigned integer with the format specifier %l in printf.

Error reporting

The compiler provides the approximate location of the syntax/semantic error in the source file.

Array out of bounds check Array indices are checked at runtime for out-of-bound accesses!

But how fast is it?

I ran some loops in python and Mini-C, and this is around 3-4 times slower than python.

That means it is horribly slow. But what was I even expecting out of a 6-day project?

Honestly, I thought this shouldn't be too far from python. So why is it slower? Lot of malloc's might be the case. And zero optimizations anywhere.

That brings me to memory management in this compiler.

It's terrible. An amazing display of profligate structures flying around from front to back (almost).

"Why the heck is an integer taking 38 bytes worth of a structure!? If, say, the source program only has 0s in it, there will be a new 38 byte structure for each one of them, eh?!" Breathtaking, literally. The program does need some space to breathe.

Atleast the AST for a function is freed once it is compiled to three address code, so the overall memory usage stays somewhat same, I hope.

Types

int, char, float and n-dimensional arrays.

There is no way to convert between types via implicit or explicit type casts.

Arrays

Since there is no dynamic memory allocation, array sizes must be declared explicitly.

So there is no way to declare arrays like here.

int size = 5;
int array[size];

It will only take around 5 more lines to get this working. But those 5 lines will take 50 minutes to write because of...

Technical Debt

It's massive.

Best to not think of it at all.

Out of, uh, header file, out of mind? A vigorous nod here, indeed. I am writing this zero days after (hopefully) finishing this project and I can guarantee I won't know what's happening in the codebase 3 days down the line.

Out of sight, out of mind; that's the correct one, lest I forget.

Statements

Almost all math expressions are allowed: These do not work on arrays.

Control flow: if-else, for, while.

Variable declarations can be aggregated with commas: int a=3, b=4;

Functions

Functions cannot have void return type. Only int, char and float can be returned. Arrays cannot be returned as well.

This limitation is only because of the syntax (there is no syntax defined to represent array types). The rest of the pipeline should support array types if type checker passes.

Note that functions cannot be recursive. This means there also cannot be mutually recursive functions and no forward declarations.

Boring, I know.

System functions

printf can be used to print whatever you want. It works like the 'real' printf(char* format, ...) where the first argument must be a character string.

time() returns current milliseconds since epoch.

exit(int status) exits the program with return value as status.

rand(int min, int max) returns a random number between [min, max).

scanInt() reads an integer from stdin and returns its value.

scanChar() and scanFloat() can be used similarly.

char[] scanString() returns a string delimited by a newline from stdin.

Running

Run bash compile.bash to compile the program. You must have yacc and lex installed.

Specify a file name as the argument above to compile and run the file:

> bash compile.bash test.mini.c

To run after compiling,

> bash compile.bash
> ./compiler filename.mini.c --dump-ast

Or, you can run a file test/filename.mini.c in the test/ directory by running

bash test.bash filename

Output dumps

You can optionally pass the flags --dump-ast, --dump-tokens and --dump-ir to the dump corresponding structures to stdout.

Output

The program outputs the three address code in a file creatde by appending .ir to source file name. This IR is executed and the output shown on stdout.

The token and AST is also dumped on stdout.

About

A compiler for a subset of C, made using lex and yacc

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published