Official Academic Guide course description.

The subjects covered in this course include: C and assembly language programming, translation of high-level programs into machine language, computer organization, caches, performance measurement, parallelism, CPU design, warehouse-scale computing, and related topics.


CS61A and CS61B (or equivalents). CS61B requirement can be bypassed if you have solid experience with a C-based programming language.


We will be using the first edition of Patterson and Hennessy’s Computer Organization and Design RISC-V Edition book (“P&H”), ISBN 0128122757. We are also requiring The C Programming Language, Second Edition by Kernighan and Ritchie (“K&R”), and will reference its sections in the reading assignments. Other books are also suitable if you are already comfortable with them, but our lectures will be based on K&R. Finally, we will be using The Datacenter as a Computer: An Introduction to the Design of Warehouse-Scale Machines (“WSC”), which is freely available online here.


There will be two midterms and one final exam.

  • Midterm 1: 2/19 8-10PM. Covers up to and including the 02/14 lecture on CALL.
  • Midterm 2: 4/10 8-10PM. Covers up to and including the 03/21 lecture on Performance, Floating Point, Tech Trends.
  • Final: 5/17 11:30AM-2:30PM. Consists of 3 sections: MT1 material, MT2 material, post-MT2 material.

On each exam, you will be given a RISC-V Green Sheet attached to the exam. Additionally, you will be allowed to bring handwritten cheat sheets as indicated below:

  • Midterm 1: One 8.5”x11”, double-sided cheat sheet.
  • Midterm 2: One 8.5”x11”, double-sided cheat sheet.
  • Final: Three 8.5”x11”, double-sided cheat sheets (it is recommended that you re-use your cheat sheets from the two midterms).

There will be no exam clobbering this semester, unlike some previous semesters.

Office Hours

We hope you take advantage of the ample office hours we have scheduled this term. When coming to office hours for lab or project help, there are some policies you’ll need to abide by. First, TA’s shouldn’t be debugging code endlessly without reason. This is not a good use of their time, and part of the goal of this course is to turn you into a great tester and debugger.

Therefore, before coming to office hours, students should have done the following on the hive machines:

  • Run valgrind and fixed all memory leaks/warnings
  • Written a test that isolates/demonstrates their issue (NOT a staff provided test)
  • Stepped through the test with (c)gdb and can tell you the line number the issue occurs on

If you have not completed all items above, a TA has the right to refuse you assistance. There are instructions for testing on all project specs, and you can review how to run valgrind and (c)gdb in lab 0.

Computer Resources

Discussion Forum

All important course announcements will be made on Piazza. Be sure to join here: https://piazza.com/berkeley/spring2018/cs61c.

Computer Accounts

You will need a CS61C class account for use in the computer labs, submitting assignments, and tracking your grades. You must request a class login via http://inst.eecs.berkeley.edu/webacct. Make sure you remember your log-in information once you change it! We cannot recover your account information for you. If you are unable to request an account due to concurrent enrollment status, please follow the instructions in lab 0. If you are a late add, you may use any other class accout, or your CS199 account until the option to create an inst account for CS61C is available to you. Note: The CS61C staff does not have any control over how quickly concurrent enrollment/late add accounts are processed.

Computer Labs

We will be using a combination of 271 Soda, 273 Soda, 275 Soda, and 330 Soda this semester. You will be receiving 24/7 key card access to these labs, but please be mindful of the fact that we share these lab spaces with other CS classes. In addition, please respect the labs by keeping things neat and avoid eating/drinking near the computers.

You can connect remotely to the lab computers using the following addresses:

  • 330 Soda (“The Hive” – Linux): http://inst.eecs.berkeley.edu/cgi-bin/clients.cgi?choice=330soda


In order to foster a collaborative environment, CS61C is graded on a fixed scale. The course is graded out of 300 points, with the following mappings from points to letter grades:

Raw Score Grade
290+ A+
[270,290) A
[260,270) A-
[250,260) B+
[230,250) B
[220,230) B-
[210,220) C+
[190,210) C
[180,190) C-
[140,180) D
[0,140) F

In the event that our distribution does not align with the EECS departmental guidelines, we may decrease the raw score boundaries, but they will not increase (i.e. it is possible to receive a higher grade than the mapping suggests, but not a lower one).

We will compute grades from a weighted average, as follows:

Assignment Percentage of Grade
Labs 5% (15 points)
Homework 10% (30 points)
Projects (5 total) 25% (75 points)
Midterm I 15% (45 points)
Midterm II 15% (45 points)
Final exam 30% (90 points)

Below, you will find sections describing some of these assignment types.


There are three categories in which you can earn EPA: Lecture participation, Discussion/Lab/OH participation, and Piazza participation. We will take the top two of your three categories to calculate your final EPA score. This means if you cannot attend lecture your EPA score will not be impacted; we will simply use your Piazza and Disc/Lab/OH totals instead.

Because you must be truly exceptional to receive full credit in any one EPA category, it is very difficult to receive a full EPA score. TAs will reward students where credit is due. EPA scores are kept internal to the course staff (i.e. not disclosed to students). Please do not inquire about your EPA score, it will not be posted.

Peer Instruction/iClickers

As you may have noticed in the “Participation” section of EPA, you will receive credit for voting on iClicker questions in lecture (your answer does not necessarily need to be correct). This is designed to give you both a break in lecture and a chance to digest the material by applying it on-the-spot. Over the course of the semester, you will be allowed to miss “a few” lectures with no penalty.

As a result, you will need to purchase an iClicker. Any iClicker that supports 5-choice multiple choice should be sufficient. As far as we are aware, this means that any iClicker should work correctly.


Labs are designed to give you introductory experience with the course material. After completing each lab, you will need to complete an in person checkoff. This process should be very quick and involves showing a TA or Academic Intern that you have completed the assignment. This staff member will then provide you with a 1 time unique code used as a verification that we have seen that you completed the lab. When you have this code you will need to make a file called tokens.txt, add the code they are given, and upload it to Gradescope. Codes cannot be shared between students and you will have a limited number of submissions to prevent attempts to “guess” a valid code. The staff is not liable for missing checkoff points and any attempts to receive credit after the deadline will not be fulfilled.

Labs are graded on correct completion. Completion of all labs is highly recommended for success in the course. Each of the labs are graded out of 2 points. Please note that these are not 2 points each from the 30 points “Labs” portion in your course grade. Each lab is simply graded out of 2 points, and we will scale the lab total up to the 30 points course grade portion.

In each lab, we will maintain two queues: a checkoff queue and a help queue. The checkoff queue is strictly for students who completed the entire lab and wish to receive the checkoff code. Ideally, checkoffs should be quick and efficient. The help queue is for students who need help completing the lab. Please do not use the checkoff queue to request help, even if it is shorter. You will only have one official checkoff attempt.

You are required to work in partners for labs. For full credit, labs must be checked off by the next lab after they were assigned. You can turn in late labs for half credit if you get them checked off the lab section after they were due.

The staff recommends always asking for help on labs when you need it, and to only request a check off when you have thought about the lab sufficiently and can have an informed conversation with your TA. Each lab will contain questions you should be able to answer, even though we will not explicit ask them to give you points. If you are unsure of the answer to any of these questions you should ask for help.


Homework is designed to give you more problem practice on the week’s material. We encourage you to work on the homework problems in small groups, but each student is required to turn in a solution that they have written themselves.

Homework is done online via gradescope and is graded on correct completion. Once again, completion of all HW is highly recommended. We will release homework solutions shortly after the due date, so late homework is not accepted.

Homeworks will give you unlimited attempts.


Projects are designed to give you heavy-duty experience with the application of course content. Projects are graded on correctness.

You will work on projects individually. Collaborating with other students is strictly prohibited. Please see the section on Academic Dishonesty below.

For each day that a project is late, 1/3 of your earned points on the project are deducted, until the project is worth nothing. Lateness rounds up to the nearest day - that is, an assignment that is 2 hours late is one day late.

Slip Days

To help you handle any issues that arise, we give you three slip-day tokens, which allow you to reduce your late penalties on late submissions.

Example usages:

  • Use two slip-days to receive no penalty on a project submitted two days late
  • Use two slip-days to receive no penalty for two separate projects each submitted one day late
  • Use three slip-days to receive just a 1/3 penalty on a project submitted 4 days late
  • We will track the total number of late days for your submissions and then assign your slip-days at the end of the semester to maximize your course score!
  • Slip-days may only be applied towards projects, and not any other assignments. Slip-days will not be assessed against projects you did not submit. No extra credit is awarded for avoiding the use of slip-days, however it is in your best interest to avoid turning projects in late. Usually, a new project will be released very shortly after the current project is due.

Academic Dishonesty and Cheating

Please carefully read the policies below and ask a member of the course staff if you have any questions or if something is unclear.

  • All projects will be done INDIVIDUALLY
  • With the exception of laboratories and assignments that explicitly permit you to work in groups, all homework and projects are to be YOUR work and your work ALONE.
  • Partner teams MAY NOT work with other partner teams on projects.
  • You are encouraged to help each other debug without viewing each other’s code. Beyond that, we don’t want you sharing approaches or ideas or code or whiteboarding with other students, since sometimes the point of the assignment WAS the “algorithm” and if you share that, they won’t learn what we want them to learn. HKN and tutoring sessions that work you through the pseudocode are not allowed. The pseudocode is sometimes the entire point! Feel free to answer questions on Piazza that help them debug (don’t share code, even snippets there). We expect that what you hand in is yours.
  • It is NOT acceptable to copy solutions from other students.
  • It is NOT acceptable to copy (or start your) solutions from the Web.
  • It is NOT acceptable to leave your code anywhere where an unscrupulous student could find and steal it (e.g., public GITHUBs, walking away while leaving yourself logged on, leaving printouts lying around, etc.
  • We have tools and methods, developed over many years, for detecting this. You WILL be caught, and the penalties WILL be severe. This software can even detect attempts to purposefully obfuscate copying. If you have questions whether a behavior is crossing the line, ask!
  • At the minimum F in the course, and a letter in your Cal record documenting the cheating.
  • Both the giver and the receiver of code are equally culpable and suffer equal penalties.

Disabled Students’ Program

The Disabled Students’ Program (DSP) is committed to ensuring that all students with disabilities have equal access to educational opportunities at UC Berkeley. They offer a wide range of services for students with disabilities that are individually designed and remove the need to reveal sensitive medical information to the course staff. If you have a medical need for extensions of exam times or assignment deadlines, these will be granted through official documentation from DSP. Please start the process at http://dsp.berkeley.edu as soon as possible to avoid delays.

If you already have documentation from DSP, please alert instructors of your accomidation needs by posting on piazza under the ‘dsp-accomidations’ folder.

Extenuating Circumstances and Inclusiveness

We recognize that our students come from varied backgrounds and can have widely-varying circumstances. If you have any unforeseen or extenuating circumstance that arise during the course, please do not hesitate to contact the instructors in office hours or via e-mail or private Piazza post to discuss your situation. The sooner we are made aware, the more easily these situations can be resolved. Extenuating circumstances include work-school balance, familial responsibilities, religious observations, military duties, unexpected travel, or anything else beyond your control that may negatively impact your performance in the class.

Additionally, if at any point you are made to feel uncomfortable, disrespected, or excluded by a staff member or fellow student, please report the incident so that we may address the issue and maintain a supportive and inclusive learning environment. Should you feel uncomfortable bringing up an issue with a staff member directly, you may consider contacting the Campus Ombuds Office or the ASUC Student Advocate’s Office (SAO).