In fairness to everyone, all projects are due by the cutoff given in the final part of the assignment. Your report should describe the project that you turned in by the deadline (see next section for report details). However, there is always the "last" bug. If you want to make some additional changes to the code and discuss them in your report and at the meeting, we may be able to take these into account in evaluating the project, particularly if the changes are small bug fixes. However, large changes to the project after the deadline, while they may be very useful for your learning, cannot fairly be treated as if they were turned in on time.
Be sure to turn in the complete sources to your project, as well as test programs and samples of assembly code generated by your compiler. You should include a brief readme file with instructions about how to build and run your compiler in the files that you turn in (not in the report).
Please write a brief (a couple of pages should be more than enough) summary of your project describing:
Your report should discuss the entire project, not just the code generation part, so we can use it to help evaluate the overall outcome. Bring your writeup with you to your project meeting. If you do finish it in advance, you can send it in using the regular course drop box. This is optional, but allows us a chance to review your report before the meetings.
Plan on meeting with the instructor during finals week for 20 minutes to discuss your project. Meetings are scheduled at UW on Tuesday, March 18, and Microsoft on Thursday, March 20. If neither of those times can be made to work, it may be possible to schedule other times; contact the instructor if this is a problem.
Please bring a copy of your report with you. This isn't a formal presentation (i.e., don't waste time preparing a PowerPoint presentation or anything like that). If at all possible, everyone in your group should be at the meeting.
That's it! Have a great spring break!