Contents of the READ.ME file

Additionally, I removed the buffers= line from my config.sysbecause the extra layer of system buffering slowed down the "disk i/o".

Also in the area of file i/o, many of the compilers have theirown unique parameters to open (and creat) and fopen. You'll probablyhave to make some adjustments in diskio, rpt and mktstfil.

The data file written by mktstfil is just one long bunch ofcharacters, 64000 to be exact. There are no line separators and nonulls.

The main driver for the entire testbed is testbed.c. Itcontains a data structure which controls the execution of all of theindividual test routines.

There is also a file called test1.c which I set up to run asingle test. This was useful for situations in which there was anerror and I didn't want to rerun all of the earlier tests (I ran thedisk tests a number of different ways).

To all of you guys with 68000 compilers, when I started toput these tests together, I had no idea that a port would be in order.Be aware that, with the exception of the drystone, this batch of codewas developed on a machine with a 16 bit int. So, if you have anyproblems because your int size is too long, change the offending intsto shorts. (Usually, the problems come in the other direction. So,my guess is that you're ok.)

With the foregoing caveats, if you have any questions orsuggestions, or if you just want to talk, feel free to call.

Good luck.

David Kessler.

This list contains a brief description of each of the .c files. It alsogroups the files into the portions of the compiler which the tests tryto exercise. I have also included the names of the individual routinescontained in each file and the description which appears on the finalreport below each file name.

Miscellaneous routines:

diskio.h some constants used by the disk referencing code (mktstfil, diskio, rpt)