espl1000
espl1000 copied to clipboard
pointbazaar
[Work in Progress] Toy Compiler <3
struct TAC should be opaque and use getters and constructor/destructor. The width of the operation: load/store/arithmetic/... should be a separate field. Its currently encoded in multiple unrelated fields for different...
currently the cli flags for 'sd' are too much handcoded. The '-help' contents are just handcoded aswell. Each flag should be an instance of a 'struct Flag' and contain the...
Since things like brne, brlt and such cannot really be used on their own for branches inside a function (they can only jump up to 64 instructions away), they all...
Currently all the tests are run sequentially, which is leaving a lot of performance on the table. To make it simple, we could run each test in it's own thread....
put the tests for lexer, parser, ast, rat, compiler, ... into one binary. This will help to expose the utility functions (test durations, etc) and any further developments there to...
when running the test, be able to specify how many values to test we have lots of loops which start at some value, then iterate until start_value + range where...
``` ./sd aaa/aaaaa.....dg ``` will segfault the thing.
To support source level debugging, source level stepping, inspecting the stack frame, ... Implementation idea: Extend ```struct Instr``` (array of which is stored in ```struct IBuffer```) with line number information....
To make it easier for self-hosting down the line.