I will be available in my office (OHS 303) from 10:30-11:20 on Tuesdays through Fridays, as well as by appointment. Or try your luck: just stop by and see whether my door is open. You may send me electronic mail at firstname.lastname@example.org or call me at extension 7466. I'll try to put any updates to my office hours on my web page, so check there if in doubt.
The final deadline for rewrites of homework problems is 1:30pm on October 13th for chapters 1-3 and appendix C, 1:30pm on November 12th for chapters 4-5, and 1:30pm on December 15th for chapters 6-7.
Unless I indicate that a particular problem must be done individually, you may work on any problem in a group of two or three students. One copy of the solution produced by the team should be turned in, with all team members' names on it. Write “we all contributed fairly to this solution” and have all team members sign under that statement.
You must show your work; a numerical answer is not an acceptable solution to a homework problem.
There will be two intra-term tests as shown on the syllabus below and a final exam as scheduled by the registrar. If you have a conflict with a testing time, please contact me as soon as possible to make an alternative arrangement.
Exams will be closed-book and mostly closed-notes. You may, however, use a single 8 1/2 by 11 sheet of paper with hand-written notes for reference. (Both sides of the sheet are OK.)
Any substantive contribution to your solution by another person or taken from a publication should be properly acknowledged in writing. Failure to do so is plagiarism and will necessitate disciplinary action.
The same standards regarding plagiarism apply to team projects as to the work of individuals, except that the author is now the entire team rather than an individual. Anything taken from a source outside the team should be be properly cited.
One additional issue that arises from the team authorship of project reports is that all team members must stand behind all reports bearing their names. All team members have quality assurance responsibility for the entire project. If there is irreconcilable disagreement within the team it is necessary to indicate as much in the report; this can be in the form of a “minority opinion” or “dissenting opinion” section where appropriate.
You are expected to be familiar with the college academic honesty honor code policy and to comply with that policy. If you have any questions about it, please ask.
If you are too sick to complete an assignment on time, you will not be penalized. Simply write “late due to illness” at the top of the assignment, sign your name and hand it in. Other circumstances will be evaluated on a case-by-case basis.
If you have a learning, psychological, or physical disability for which a reasonable accommodation can be made, I would be happy to refer you to the college's disability services coordinator and to cooperate in the accommodation process. It is generally best if this can be done as soon as possible.
Sections shown in italics are on the CD-ROM accompanying the textbook.
|9/9||1.1-1.3||Computer abstractions and technology|
|9/11||2.1-2.4||Instructions, especially arithmetic|
|9/15||2.8-2.9||Procedures and strings in assembly|
|9/16||2.10-2.12||More on assembly programming|
|9/17||B.1-B.6,B.9||Assembly programming tools|
|9/18||2.13-2.14||Assembly programming examples|
|9/21||Lab 1: Elementary assembly programming|
|9/22||2.16-2.19||Yet more on assembly language|
|9/23||Lab 1 (continued)|
|9/25||Lab 1 (continued)|
|9/28||3.5-3.6||Floating point arithmetic|
|9/29||Numerals: cross-cultural perspective||Lab 1|
|9/30||Lab 2: More advanced assembly programming|
|10/2||Lab 2 (continued)|
|10/6||No class (attend Nobel Conference)|
|10/7||No class (attend Nobel Conference)|
|10/8||Extra office hour|
|10/9||Lab 2 (continued)|
|10/12||Lab 2 (continued)|
|10/13||Review; catch-up||HW rewrites (1-3,C)|
|10/14||Intra-term test 1|
|10/15||4.1-4.3||A simple datapath|
|10/16||4.4||A single-cycle processor|
|10/19||Lab 2 (continued)|
|10/21||Lab 2 (continued)|
|10/22||4.6-p.358||A pipelined datapath|
|10/23||4.6||Pipelined control||Lab 2|
|10/26||No class (reading day)|
|10/27||No class (reading day)|
|11/2||4.10-4.11||Advanced instruction-level parallelism|
|11/6||Lab 3: Memory system performance|
|11/9||5.5-5.6||Memory hierarchies and virtual machines|
|11/11||Lab 3 (continued)|
|11/12||Review; catch-up||HW rewrites (4-5)|
|11/13||Intra-term test 2|
|11/16||7.1-7.5||Multiprocessors and multithreading|
|11/17||7.6-7.7||SIMD, vector, and graphics processors|
|11/18||Lab 3 (continued)|
|11/19||A.1-A.7||Graphics processing units|
|11/23||Lab 3 (continued)|
|11/24||No class||Lab 3|
|11/25||No class (Thanksgiving)|
|11/26||No class (Thanksgiving)|
|11/27||No class (Thanksgiving)|
|11/30||Lab 4: Multiprocessor performance|
|12/1||7.10-7.13||Roofline performance model|
|12/4||Lab 4 (continued)|
|12/7||Lab 4 (continued)|
|12/9||Lab 4 (continued)|
|12/10||6.10||An example I/O system|
|12/14||More on networks|
|12/15||Review; catch-up; evaluation||HW rewrites (6-7)|
Course web site: http://gustavus.edu/+max/courses/F2009/MCS-284/