CSE 131 - Turn-in Instructions
All testing and grading of assignments will be performed on
ieng9.ucsd.edu, in the prep cs131s environment.
To be graded at all, YOUR ASSIGNMENT MUST BE TURNED IN BEFORE THE DUE DEADLINE
using the Turn-in Procedure described below. Late turnins will not be
The TURNIN will allow working and non working code to be submitted.
Code submission DOES NOT imply successful or working code - only that
your file(s) have been submitted for grading.
WE LOG ALL TURNIN TRANSACTIONS - both successful and erroneous.
1.) We will be testing your program by doing a "make new". If you do modify
your Makefile, ensure "make new" still results in compiling your code.
2.) Remove all debugging output before you turnin your project. This
includes both stdout and stderr messages. Your error messages should only
displayed in stdout. We will also monitor stderr to catch Java Exceptions.
Turn-in Procedure for Project #1 - Semantic Checking
Turn-in Procedure for Project #2 - Code Generation
Same as project 1 above.
All output in the generated assembly file must go to stdout. No
debugging output should occur in the assembly file, stdout, or stderr. Debugging comments
in the generated assembly file is fine.
The TURNIN runs a very SIMPLE test case:
function : int foo()
function : void main()
x = 3 + 5;
cout << x << foo();
You certainly should fix any errors it finds,
but you will also want to do additional extensive testing of your
Correct output of the SIMPLE test case:
Below is your program's output: CORRECT
Incorrect output of the SIMPLE test case:
Below is your program's output: INCORRECT
(your program's output here)
If you are working in a team of 2, run TURNIN from one of your
two accounts only!