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) or experience with a C-based programming language (e.g. Java, C++).
There is no official textbook for this class. However, there are three optional textbooks as additional references:
- P&H: Second edition of Patterson and Hennessy's Computer Organization and Design RISC-V Edition book ("P&H"), ISBN 0128122757.
- K&R: The C Programming Language, Second Edition by Kernighan and Ritchie. Other C programming books are also suitable if you are already comfortable with them, but our lectures will be based on K&R.
- WSC: The Datacenter as a Computer: An Introduction to the Design of Warehouse-Scale Machines, which is freely available on our website.
Please contact staff on Ed if you have trouble finding or paying for these textbooks.
The following sub-sections contain an overall summary of the major elements of the course.
We will have a 50-minute live lecture on Mondays, Wednesdays and Fridays, 10:00AM–11:00AM PT. Lectures will take place in Valley Life Sciences Building (VLSB) 2050. We will try to livestream lectures live on Zoom as well. Recordings will be made available after the lecture.
Weekly 1 hour long discussion sections will be held on Wednesdays and Thursdays. Discussion section attendance is not graded, and you can choose to attend any discussion section you want. We may hold hybrid discussion sections (see calendar), and we'll also try to post recordings.
Homework is designed to let you practice the material covered in lecture. 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 submitted online through PrairieLearn and graded on correctness. For each day that a homework submission is late, 1/3 of your points will be deducted. The lateness penalty rounds up to the nearest day - that is, an assignment that is 1 day and 5 seconds late will receive a 2/3 late penalty.
Labs are designed to give you some hands-on experience with the course material. Weekly 2 hour long lab sections will be held on Mondays. Lab section attendance is not graded. We may hold hybrid labs (see calendar), but we will not release recordings. The first hour of each lab section will be a review of the topics covered in the lab, while the second hour will be a "lab party" style work time for students to work on the lab with other students in the lab. During the second hour, students can request for help from a staff member using the office hours queue. You can choose to attend any lab section you want, or work on labs asynchronously. You may optionally work on each lab with one partner.
Lab assignments are autograded on Gradescope. For each day that a lab submission is late, 1/3 of your points will be deducted. The lateness penalty rounds up to the nearest day - that is, an assignment that is 1 day and 5 seconds late will receive a 2/3 late penalty.
Projects are designed to give you heavy-duty experience with the application of course content. We'll have four projects throughout the course. You may optionally work with one partner for each project. You may not add, change, or remove partners after creating the project repo.
Projects are submitted to Gradescope and graded on correctness. If you complete a project with a partner, make sure to add your partner on every Gradescope submission. Also make sure you "activate" the submission you want graded on Gradescope (this defaults to the last submission you made). For each day that a project submission is late, 1/3 of your points will be deducted. The lateness penalty rounds up to the nearest day - that is, an assignment that is 1 day and 5 seconds late will receive a 2/3 late penalty.
There will be one midterm, tentatively scheduled for Tuesday, March 7th, 7:00 PM - 9:00 PM PT. The final exam will be Tuesday, May 9th, 3:00 PM - 6:00 PM PT. Both exams are in-person. One alternate exam will be offered immediately after the scheduled time for direct exam conflicts. All other requests will be considered on a case-by-case basis. An exam alterations form (required for all alternate exam accommodations) will be released closer to the exam.
Logistics will be announced in the weeks leading to the exam.
TAs and instructors will hold in-person and online office hours throughout the semester. We use an OH Queue to process help tickets.
Please do not expect TAs to debug your code. 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. However, the TAs can help you find and fix your bugs.
Therefore, before coming to office hours, you should have:
- Run valgrind and fixed all memory leaks and compiler warnings
- Written a test that isolates/demonstrates the issue (NOT a staff-provided test)
- Stepped through the test with a debugger to find the area of code with the issue
- Checked that the problem still occurs on the hive machines, unless the assignment supports local machines
If you have not completed all of the items above, a TA will request that you complete them before they can help you. There are instructions for testing as part of all project specifications, and the first few labs cover Valgrind, (C)GDB, and debugging.
Please mark your tickets as conceptual or debugging. For conceptual tickets, TAs will help groups of students at a time (shorter wait time) but cannot look at code. For debugging tickets, TAs will look at you or your group's code, but time per ticket may be limited if the queue is long.
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:
|Assignment||Percentage of Grade|
|Labs||10% (30 points)|
|Homework||10% (30 points)|
|Project 1||10% (30 points)|
|Project 2||10% (30 points)|
|Project 3||10% (30 points)|
|Project 4||10% (30 points)|
|Midterm||16% (48 points)|
|Final||24% (72 points)|
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). Please note that we will not include PNP students or incompletes in any adjustments we do.
All important course announcements will be made on Ed (the course discussion forum). We will be automatically enrolling everyone.
- Search before posting. Your question may have already been answered by us or other students in the past. Reading other students' posts will let you refine your question, and gives us more time to answer new questions.
- Try to avoid open-ended or vague questions such as: "How does C work?" or "How come the solution to a discussion problem is this?". If you walk us through your thoughts and reference specific lines that you find confusing, we can better address the problem you are facing. Being specific helps us uncover any misunderstandings that you may have.
- Post questions about assignments as public follow-ups on the corresponding assignment post. For example, post your questions about Homework 1 on the Homework 1 post. If your question is too detailed or revealing to fit as a follow-up, your question would be better answered during office hours.
- Only post in the "answer" box if you are fairly certain about your answer. Do not post follow-up questions or +1 as an answer.
- No follow-up +1's. Instead, you should use the heart button on a question/follow-up. Excessive +1 follow-ups clutter the post and make it more difficult to get to the unresolved follow-ups.
- If you want a reply on a follow-up, mark it as unresolved, or we may not see it.
Note: If you are blocked from accessing our resources, you can use the campus VPN.
You will need a CS 61C instructional account to access computer labs and instructional servers for assignments. Accounts are available starting on the first day of instruction, and will be covered in Lab 0.
Registered students get 24/7 cardkey access, starting on the first day of instruction, to the computer labs in Soda Hall (Soda 271, 273, 275, 277, and 330). Please be mindful of the fact that we share these lab spaces with other CS classes, and please follow the Rules of Conduct on EECS Instructional Computers.
You can also remotely connect to instructional computers for class work. This will be covered in Lab 0. If you're connecting from off-campus, you must be connected to the campus VPN (as described in lab 0).
We believe that most students can distinguish between helping other students understand course material and cheating. Explaining a subtle point from lecture or discussing course topics is an interaction that we encourage, but you must write your solutions strictly by yourself. You must not ask for homework/project solutions on Stack Overflow or other online sites; although you may ask for help with conceptual questions. You must not receive help on assignments from students who have taken the course in previous years, and you must not review homework or project solutions from previous years.
You must ensure that your solutions will not be visible to other students. If you use GitHub or another code hosting platform to store your solutions electronically, you must ensure your account is configured so your solutions are not publicly visible. Many platforms offer free private repositories that allow you to keep your solutions private.
Warning: Please take a moment to review the Department Policy on Academic Misconduct. In particular, you should be aware that copying or sharing solutions, in whole or in part, from other students in the class or any other source without acknowledgement constitutes cheating.
As both current and former students, we understand that desperate times can lead to desperate measures. If you feel like you cannot succeed on your own in the course, let us know! We are here to support you.
For assignments that allow partners, you may collaborate however you like with your partner, as long as you follow the policies above. For example, sharing code with your partner is fine, but sharing code with other groups is not.
We will be running advanced plagiarism detection programs. The tools and methods for detecting cheating have been developed over the course of many years, and attempting to obfuscate your code to avoid detection:
- won't work
- will be penalized
Plagiarism on any assignment will be reported to the Center for Student Conduct. The CSC treats most first-time offenses as a Non-Reportable Warning. Additionally we will assign a grade penalty. The minimum penalty for cheating on an assignment is negative points, so if an assignment is worth 10 points you will receive -10 points. This means even if there is just a 50% chance that you are caught it is better to not do the work than attempt to cheat. A second instance of plagiarism on an assignment will result in an F in the course.
Disabled Students' Program
The Disabled Students' Program (DSP) supports disabled students at UC Berkeley. They offer a wide range of services and accommodations. If you are facing barriers in school due to a disability, apply to DSP!
Students registered with DSP can expect to receive an onboarding email within two weeks of sending us your formal letter of accommodation through the AIM portal.
As instructors, our goal is to teach you the material in our course. The more accessible we can make it, the better.
Accommodations and Extensions
- Extension Requests: This is to request extensions on deadlines for any assignments.
- Requests will be reviewed approximately every two business days.
- Extensions may not be visible on Gradescope and PrairieLearn, but they will show up on grading reports.
- You can submit an extension request at any time, including after a deadline.
- Extenuating Circumstances: This form is for any circumstances that can't be resolved with extensions. This form is visible to all student support TAs, head TAs, and instructors. You can also email cs61c@ for extenuating circumstances, and it will be only visible to the head TAs and instructors. Don't be afraid to reach out! We're here to help you succeed in our course.
Extenuating Circumstances and Inclusion
We recognize that our students come from varied backgrounds and have widely-varying experiences. If you encounter extenuating circumstances, please do not hesitate to let us know. The sooner we are made aware, the more options we have available to us to help.
In addition, in scheduling exams, we have attempted to avoid conflicts with major religious holidays. If, however, we have inadvertently scheduled an exam or major deadline that creates a conflict with your religious observances, please let us know as soon as possible so that we can make other arrangements.
If something is said in class (by anyone) that makes you feel uncomfortable, disrespected, or excluded by a staff member or fellow student, please report the incident so that we can work to address the issue and create a more supportive and inclusive learning environment. Some options:
- via the 61C incident reporting form
- via email to our instructors, head TAs, or another member of staff you're comfortable with
- to the department's Faculty Equity Advisors (CS) Prof. Josh Hug email@example.com or (EE) Prof. Robert Pilawa-Podgurski firstname.lastname@example.org, the UC Berkeley Campus Ombuds Office or the ASUC Student Advocate's Office (SAO)
- via the department's Student Climate and Incident Reporting Form
- via the EECS Student Grievance Committee
Your mental health is more important than this course. Seriously. If you're feeling overwhelmed or not in control, talk to us and we'll try to help. Counselling and Psychological Services (CAPS) has multiple free, confidential services:
Also check out UHS's mental health resources
Support is also available for survivors of sexual violence or harassment. While course staff are Responsible Employees for such incidents, we do have free, confidential services available on campus:
The National Suicide Prevention Lifeline is a 24-hour number any student or faculty/staff person can call to speak with someone about suicide: +1-800-273-TALK (+1-800-273-8255).
If you're in need of laptops, Wi-Fi hotspots, or other required technologies, check out the Student Technology Equity Program.