|
|
||
|---|---|---|
| .. | ||
| bin | ||
| lib | ||
| llprograms | ||
| test | ||
| .ocamlformat | ||
| .ocamlinit | ||
| dune-project | ||
| hw3.opam | ||
| Makefile | ||
| README.md | ||
| submit_zip_contents.txt | ||
HW3: LLVMlite backend
Quick Start:
- open the folder in VSCode
- start an OCaml sandbox terminal
- run
make testfrom the command line - open
bin/backend.ml
See the general toolchain and project instructions on the course web site. The course web pages have a link to the html version of the homework instructions.
Using oatc
oatc acts like the clang compiler. Given several .ll, .c, and .o files, it will compile the .ll files to .s files (using the cs131 backend) and then combine the results with the .c and .o files to produce an executable named a.out. You can also compile the .ll files using clang instead of the cs131 backend, which can be useful for testing purposes.
-
To run the automated test harness do:
./oatc --test -
To compile ll files using the 131 backend:
./oatc path/to/foo.ll- creates output/foo.s backend assembly code
- creates output/foo.o assembled object file
- creates a.out linked executable
NOTE: by default the .s and .o files are created in a directory called output, and the filenames are chosen so that multiple runs of the compiler will not overwrite previous outputs. foo.ll will be compiled first to foo.s then foo_1.s, foo_2.s, etc.
-
To compile ll files using the clang backend:
./oatc --clang path/to/foo.ll -
Useful flags:
Flag Description --print-ll echoes the ll program to the terminal --print-x86 echoes the resulting .s file to the terminal --interpret-ll runs the ll file through the reference interpreter and outputs the results to the console --execute-x86 runs the resulting a.out file natively (applies to either the 131 backend or clang-compiled code) -v generates verbose output, showing which commands are used for linking, etc. -op <dirname>change the output path [DEFAULT=output] -o change the generated executable's name [DEFAULT=a.out] -S stop after generating .s files -c stop after generating .o files -h or --help display the list of options -
Example uses:
Run the test case llprograms/factrect.ll using the 131 backend:
./oatc --execute-x86 llprograms/factrect.ll --------------------------------------------------------------- Executing: a.out * a.out returned 120