Toy Compiler Projects

Hand-code both toy compilers (hand-written parser and generated parser). These projects are solely to practice using make, gcc, bison, flex, and git to develop, build, and run software. Since the goal of this is not to design and implement the compilation algorithms for yourself, toy compilers may not be turned in late, since they only require hand-entering and running the code.

You may use the code developed live in class. You must, however, enter the code yourself by hand, without any digital copying from student or others' versions of the code. This will help ensure you have comfort with the style of C and programming tools used for the SimpleC Compiler programming project that you will design and implement individually.

To submit these projects, accept the GitHub assignment for "Toy Compiler 1" and "Toy Compiler 2" from the link in Webcourses, and submit your answers to GitHub. Please do not create or copy the repository to your personal GitHub page, since this violates UCF's Golden Rule policies.

Read over the lecture notes covering the hand-written toy compiler.

1. Be sure that your virtual machine is setup.
2. Enter your virtual machine vagrant ssh.

3. Create the git repo using the Toy Compiler 1 assignment link in webcourses, clone it in your virtual machine and enter the newly created directory.

   git clone git@github.com:cop3402/toy-compiler-1-USERNAME
   cd toy-compiler-1-USERNAME
   

4. Hand-write all the source code for the toy compiler using the images in the starter repository.
5. Double-check that it is working correctly using the instructions below.
6. Submit the project to your toy compiler repository.
7. Double-check that all the files are in your GitHub repository by visiting its link or running git clone YOUR_REPO_URL to verify that graders will have access to it.

Read over the lecture notes about using the parser generator to replace the hand-written parser in the toy compiler.

1. Create the git repo using the Toy Compiler 2 assignment link in webcourses, clone it in your virtual machine and enter the newly created directory.

   git clone git@github.com:cop3402/toy-compiler-2-USERNAME
   cd toy-compiler-2-USERNAME
   

2. Hand-write all the source code for the toy compiler using the images in the starter repository.
3. Double-check that it is working correctly using the instructions below.
4. Submit the project to your toy compiler repository.
5. Double-check that all the files are in your GitHub repository by visiting its link or running git clone YOUR_REPO_URL to verify that graders will have access to it.

It's important to validate that your toy compiler both builds and runs as expected. From inside of your source code repository directory, run the following:

make  # build the toy compiler
cat template_start.s <(cat example.toy | ./toy) template_end.s > example.s  # run the toy compiler, will echo the input in toy compiler 2
diff -w example.s.expected example.s  # compare the output, will not print anything if the files math
gcc -o example example.s  # assemble the output
./example  # execute the output program, this will output the results of the calculations in the example.toy program

Submit your project using git to add source, commit changes to them, and push your local repository to the GitHub repo as described in class. Put the Makefile and all source files in the root of the source code repository; there is no need to create a subfolder.

It is important to validate that your source code repository has the necessary files to build and run your project. You can check this by going to a new directory (somewhere besides your current toy compiler source directory) and recloning your repository, i.e.,

# in a directory other than your toy compiler directory
git clone git@github.com:cop3402/toy-compiler-1-USERNAME toy-compiler-1-test-repo
cd toy-compiler-test-repo

(Be sure to substitute USERNAME with your actual GitHub user name.)

Then try to build and run your project as described above.