4003-520/4005-720 Computer Architecture , Spring 20103

What's New

• May 11th: Corrected the targets for try for the group project NEW/Updated
• May 4th: Added the answers to Homework 5
• April 28th: Homework 5 is now available
• April 14th: Homework 4 is now available
• April 6th: Added a note about things you can bring to the exam
• April 5th: Added the answers to Homework 3
• March 29th: Homework 3 is now available
• March 26th: The second project is now available.
• March 21st: Homework 2 is now available
  March 21st: The group project is now available.
• March 15th: The first project is now available.
• March 12th: Homework 1 is now available
• March 07th: New quarter

Syllabus

• 4003-520 Undergrad Syllabus
• 4005-720 Grad Syllabus
• 4005-720 Research Topic Requirements

ICSS520 Homework

NOTE all homework is due at the beginning of class.

• Homework 1: Due date: March 22
• Homework 2: see paper handout for homework: Due date: March 29
• Homework 3: Due date: April 5
  Homework 3 answers
• Homework 4: Due date: April 21
  • Answer sheet for A.1a
• Homework 5: Due date: May 3
  Homework 5 answers

Projects

NOTES for all projects
• 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



• Project 1 Due date: March 29th
  Supporting Documentation
  • 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.
• Project 2 Due date: April 12th

Group Project

• Group Project
  • The submission targets were incorrect in the previous version of the document (they have been corrected now). The new targets are: NEW/Updated
    • try grd-720 project-103 CPU.C README ADDENDUM PROGRAM_FILES
    and for the evaluations
    • try grd-720 103-team EVAL

  Component	Due Date
  Initial Project meeting (last date)	Thur March 31st
  ISA document	Thur April 14th
  Hardware & CU document	Tue May 3rd
  Initial Project Demo	Thur May 5th
  Final Project	Tue May 17th

Exams

Exam	Date/Time	Location	Study Guide	Review Session	Notes
Exam 1	Week 5: April 7th	In Class	Topics List		see Note 1 below
Exam 2	Week 10: May 12th	In Class	Topics List		see Note 1 below

Exam Notes

Note	Note
1	You are allowed to bring a non-programmable calculator and a single 8.5x11 sheet of paper with hand written notes to the exam.

Topic Schedule

Unless otherwise noted, all overheads are taken from Prof. Carithers class notes

Topic	Book Chapter	Notes
Digital Design review notes Computer Organization review notes	Review of Computer Organization (4003-345)	Things you should know from the pre-reqs
Comp. Arch. Introduction Notes on the Arch library	Notes
Comp. Arch. cost and performance	1
Control Unit Design	Notes
Instruction Set Architecture	Appendix B
Pipelining Scoreboarding Dynamic Branch Prediction	Appendix A, 2, 3
Memory Hierarchy Improving Cache Performance	Appendix C, 5
Multithreading	3
Multiprocessors	4
I/O Systems - from notes by Dr. Guihai Chen	Class Notes

• more notes will become available as times goes on

Computer Architecture Resources at Other Sites

• Home page for our textbook
  Contains links to PDF versions of the appendices, and other bits and pieces of useful information.

• WWW Computer Architecture Page at the University of Wisconsin
  Lots of links to tools, simulators, people, conferences, etc.

• David Patterson's home page at Berkeley
  Co-author of our textbook; links to his courses, and other references.

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 Organization and Design 4th edition by Patterson and Hennessy. Morgan Kaufmann 2009

  Specificly look for information in:

  • Chapter 4, The Processor
  • Appendix D, Mapping Control to Hardware

  Note this book is used by the Computer Organization class (4003-345 & 4003-710) so should be available in the bookstore.

• Notes about the arch library:
  • A simple document describing the structure of the arch library: PostScript, PDF
  • 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)).

• 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:
• breaking code up into multiple files of reasonable length
• 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.