From kenmac Mon Aug 27 20:54:32 -0400 2001
From: "Kenneth M. Mackenzie" <kenmac@midway.cc.gatech.edu>
To: gte245i@prism, gte278u@prism, gtg036e@prism, gte871j@prism, gte336p@prism, gtg002c@prism, gte437j@prism, gte727m@prism, gtg970b@prism, gt7110b@prism, gtg157e@prism, gt7286b@prism, gte434h@prism, gt8929a@prism, gte029s@prism, gte896k@prism, gte064f@prism, gt7252b@prism, gte550w@prism, gte295r@prism, gte858t@prism, gte513w@prism, gtg370c@prism, gte220u@prism, gte857t@prism, gtg304c@prism, gte992r@prism, gte812e@prism, gte025e@prism, gte564q@prism, gt7934c@prism, gtg692c@prism, gtg607c@prism, gtg814c@prism, gtg700c@prism, gtg302c@prism, gt0916a@prism, gt8664a@prism
Subject: homework1
Reply-to: kenmac@cc.gatech.edu

Hi all,

  Here are a few notes on homework 1 based on questions after class.
What I like to do when I have a correction or clarification message
like this is to send it by e-mail and also archive it on the web site.
E.g., this will be "homework1-note1.text" on the web site next to
homework 1.

1. Working in pairs means you can turn in one homework with two names
   on it.  I.e., you can write one program.

2. The test program for testing mips is pretty much as easy as it
   sounds:  write a program in C whose execution time will be
   proportional to the MIPS rating of the machine, then measure the
   execution time of the program.

   Make sure the program runs for a few seconds at least, otherwise
   you're probably just measuring startup effects.

   There's a skeleton program "mips.c" on the web page that uses calls
   to gettimeofday to measure execution time in seconds.  You can use
   this skeleton and add your own code into the middle of it.

3. To test gcc, you need a test program of a reasonable size.  Use the
   test input for CC1 as used in project1:

    gcc -O2 -c -o /dev/null /net/projects/class/6290/fall01/project1/cc1/cc1.i

regards,
-- Ken