- all Projects are electronically submitted and are due at 11:59:59pm on the specified date.
- A series of tests will be run against your project submission; however, only some of these will be displayed as they are run.
- IF YOU INTERRUPT 'try' BEFORE IT COMPLETES, NONE OF YOUR FILES WILL BE SUBMITTED.
- You may find Prof. Carithers common project Q/A from previous quarters file to be helpful.
- A couple students have put done some work to get the arch package to compile under gcc. Here are the gcc notes
Supporting Documentation
- Computer Architecture: The M043 CPU, Document containing the description of the M043 machine.
- NOTE the provided sample object file(s) may not cover all the possible instructions, no less all the possible interesting conditions of the instructions. I highly recommend that you create some of your own files for testing.
Supporting Documentation
- A PDF description of the IMPS architecture and control flow diagrams.
- FAQ for Project 2
- A few errors were found in the RTL inside the IMPS architecture
document (April 17):
NEW
- RTL for SLT and SLTI were incorrect
- The Trap inst with opcode=3F (not the special trap) is a J-type instruction, and the trap number is in the abs field (not in the imm field as was specified).
- RTL for BGEZ was incorrect.
- Found some more problems with the RTL (April 28):
NEW
- The effective address for all the load and store instructions was written wrong. It has now been corrected.
- The register containing the data to store was incorrectly.
Exams
- Topics List for exam 1
- A help session for the exam will be held in the CS Conference room (70-3000) April 6th from 4-5pm NEW
- Topics List for exam 2
Exam 1
-
The planned date for exam 1 is during week 5:
April 6th
Exam 2
-
The planned date for exam 2 is during week 11:
May 16th
Class Overheads
Unless otherwise noted, all overheads are taken from Prof. Carithers class notes- Comp. Arch. introduction and Notes on the Arch library
- Comp. Arch. cost and performance
- Control Unit Design
- Instruction Set Architecture
- Pipelining
- Scoreboarding
- Dynamic Branch Prediction
- Memory Hierarchy
- Improving Cache Performance
- I/O Systems - from notes by Dr. Guihai Chen
- more notes will become available as times goes on
Documents
- NOTE, make sure your
NAME is on every document and file you send to me.
- All assignments need to be handed to me directly, or turned in to
the Computer Science Office (70-3005) on the specified due date.
I DO NOT ACCEPT ASSIGNMENTS THAT HAVE BEEN SLID
UNDER MY OFFICE DOOR!
- Refence book for information on control sequencers:
Computer System Architecture 3rd edition by M. Morris Mano, Prentice-Hall Inc. 1993
Specificly look for information in:
- Chapter 5, Basic Computer Organization and Design
- Chapter 7, Microprogrammed Control
Note this book is used by the Computer Organization class (4003-352) so should be available in the bookstore.
- Notes about the arch library:
- A simple document describing the structure of the arch library: PostScript, PDF
-
C++ Architecture Library documentation produced by Rational Rose
is available in
HTML and
MSWord format.
For those who want a better view of the relationships between the various classes in the arch2-2 library. - You may find Prof. Carithers answers to common questions about the arch library to be helpful.
- Prof. Carithers description of the arch library object module format may be useful if you want to build your own test programs.
-
Computer Architecture: Design Using RTL, an introduction to
the use of RTL in design (from
0603-352, Computer Organization)).
-
Computer Architecture: Microprogrammed Control Units, an
introduction to microprogrammed design (from
0603-352, Computer Organization)).
-
Preparing color transparencies for printing
- The color printer is loaded with transparencies, which are fairly expensive commodities, so it is important that you prepare your slides properly and preview them before printing to avoid waste (and to keep us from having a lab fee!)
-
WML services: preparing color transparencies
-
CS 4 standards document for C++.
Note these are only a guideline for how I want your code to look. Specifically I want your code to be neat, clear, and consistent. I'm looking for: - reasonable length functions
- program file headers with your name
- function and class headers
- clear and consistent indentation
- Beginners guide to high performance computing (some nice definitions). High Performance Computing . A little simple, but it could be useful.
Phil's home Page