CMSC 311 - Project #1

computer organization

c m s c 311
s p r i n g 2 0 0 3

Project #1 Submit Directions

Additional Info: Handling Escape Sequences

You should handle \n, \t, \", and \\. That is, if the binary contains the ASCII code for newline, tab, double quotes, or backslash, you should print out \n, \t, \", and \\.
Surrounding quotes do NOT appear in the binary file. For example:
```
foo: ascii "cat"
```
The two double quotes do NOT appear in the binary file. Just the characters for 'c', 'a', 't'.
You can submit the assembler extra credit separately, but all other extra credit and parts must be submitted in one submssion. Directions for submitting the assembler will be provided later (after Spring Break).
Clarification: if the file ends in .bin, replace the extension with a .asm (e.g., foo.bin is the input, and foo.asm is the output). All other files should add the extension .asm. (e.g. foo.foo is the input, and foo.foo.asm is the output).
The number of array elements in the assembled file (e.g., input.dat) will always match the size of the array (although the size of the array is "off-by-one" from the value in the assembled file, e.g., if you read in a "1" from the file, that really means 2 array elements). The only time you worry about missing numbers in the array is when you write the assembler. If the file with the .data in it has arrays declared, it can be missing numbers. This is not the case with the assembled binary file---the number of array elements always matches the array size.
The assembler is the extra credit and is NOT due on Friday. It should be turned in separately.

Submit Instructions

First, the submit script should be ready by Wednesday at some point. Look for the announcements to indicate when it's properly working. Right now, something buggy is going on, and I need to investigate that.

To submit, you will type:
```
~chs11001/submit p1.tar 1
```
You should submit ONE tarfile. That tarfile should consist of:
- Makefile or makefile
  The makefile should make two targets. This is roughly how your Makefile should look:
```
....macros go here....

all: hexdump disassem

hexdump: ...dependencies for hexdump..

disassem: ...dependencies for disassem..
```
  When you run "make", it sees the dependencies as hexdump and disassem. Then, you just have makefile stuff as if you were doing two different makefiles.
  It should create a hexdump and disassem executable.
- README
  This should indicate what extra credit you did.
- Source code, etc.
  Obviously, we need to compile something. In general, we'll just test the executable. The main exception is byteToHex function, just to see it works.
You should follow the following conventions. Any C++ source file should end in .cpp. Any C source file should end in .c.
If you wrote byteToHex.cpp, it should compile with cxx -w0 std strict_ansi (which usually means it can handle g++).
If you wrote byteToHex.c, it should compile with cc.
Other than that, I have no real restrictions on whether you use g++ or cxx.

Note: the submit script will NOT test your tar file. You will be allowed to submit anything with a Makefile and a README included in the tarfile. If it fails to make the correct executables, you may lose points, and then be asked to resubmit. Penalties are likely to be about 10%. So be careful!

See the class syllabus for policies concerning email
Last Modified: Fri Feb 14 09:13:38 EST 2003

Web Accessibility