Note: This website is under construction. All content is tentative and subject to change.


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) or experience with a C-based programming language (e.g. Java, C++).

Optional Reading

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.

Course Format

The following sub-sections contain an overall summary of the major elements of the course.


We will have an 80-minute live lecture on Mondays, Tuesdays, Wednesdays and Thursdays, 2:00 PM–3:30 PM PT. Lectures will take place in Valley Life Sciences Building 2050. Recordings will be made available after the lecture, but lectures will not be livecasted to Zoom.


One hour long discussion sections will be held twice a week on Mondays and Wednesdays. We intend to offer at least one remote discussion section, subject to staff availability. You can choose to attend any discussion section you want. Discussion section attendance is not graded.

We may release pre-recorded discussion walkthroughs, though they are meant as a supplementary material.


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.


Labs are designed to give you some hands-on experience with the course material. Two-hour long lab sections will be held twice a week on Tuesdays and Thursdays. We intend to offer at least one remote lab section, subject to staff availability. Lab section attendance is not graded. 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. You can choose to attend any lab section you want, or work on labs asynchronously. We encourage you to work on the labs in small groups, but each student is required to turn in a solution that they have written themselves.

Lab assignments are autograded on Gradescope.


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. Partnerships must be registered on Gradar, and adding another student to your Gradescope submission does not create an official partnership.

If you choose to work with a partner, all work must be done synchronously in a pair-programming fashion. By creating a partnership, both you and your partner are responsible for the work in your repository and the work you submit.

Projects are submitted to Gradescope and graded on correctness. If you complete a project with a partner, you must add your partner to every Gradescope submission. Also make sure you "activate" the submission you want graded on Gradescope (this defaults to the last submission you made).


There will be one midterm, scheduled for Thursday, July 11th, 7:00 PM - 9:00 PM PT.

The final exam will be Wednesday, August 7th, 3:00 PM - 6:00 PM PT.

Exams are in-person, no exceptions.

The midterm is scheduled for Thursday, July 11th, 7:00 PM - 9:00 PM PT. There are no alternate exams. If you have a conflict, you can clobber your midterm with the final.

The final exam is scheduled for Wednesday, August 7th, 3:00 PM - 6:00 PM PT. One in-person alternate final from 6:00 PM - 9:00 PM PT will be offered for direct exam conflicts.

If you have exam accommodations, we will reach out with exact times in the next week or so.

If you feel unwell before an exam, please notify staff ASAP. If you take the exam while sick, we will void your exam score. Please respect the health of other students and our staff!

The exam adjustments form (required for all alternate exam accommodations), along with more detailed logistics, will be released closer to each exam.

Exam Clobber

If you score better on the final, we will use the z-score of your final exam score to replace your midterm score.

Office Hours

TAs and instructors will host mostly in-person and extremely few 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.

If you are attending an online office hours block, you can find the zoom link on the EdStem. To receive help, enter any open breakout room, make a ticket on the OH Queue, and remember to note which breakout room you're in.


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:

Course PointsGrade
AssignmentPercentage of Grade
Labs10% (30 points)
Homework10% (30 points)
Project 110% (30 points)
Project 210% (30 points)
Project 310% (30 points)
Project 410% (30 points)
Midterm16% (48 points)
Final24% (72 points)

At the end of the semester, the A+ bin, which is reserved only for students with exceptional performance in the course, will be determined by the instructors.

Each lab is worth 3 course points. The first 3 homeworks are each worth 6 points, and the remaining 4 homeworks are each worth 3 course points.

The bins will not change (i.e. we will not shift the bins or round at the end of the semester). Grade bins target a 3.3 GPA, assuming 65% average on exams and 95% average on other assignments. To normalize exam difficulty variance across semesters, we will do the following: if the exam average is higher than 65%, then nothing will change; if the exam average is lower than 65%, we will adjust the denominator such that the exam has a 65% average. Scores are capped at 100% (i.e. you cannot have a score over 100% from this).

Late Enrollment

If you enroll in the class late, please email cs61c@ so we can work out a schedule of deadlines. However, we cannot guarantee an extension on all assignments in the interest of keeping you up to pace with the rest of the course. Our default assumption is that any student who enrolls late will be able to catch up within 2 days of enrollment.

Course Announcements and Computer Resources

Ed (EdStem)

All important course announcements will be made on Ed (the course discussion forum). We will be automatically enrolling everyone. We will not be answering private Ed questions unless directed by a staff member in office hours.

Ed Etiquette

  • 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.

Computer Resources

Note: If you are blocked from accessing our resources, you can use the campus VPN.

Computer Accounts

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.

Computer Labs

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).

Collaboration and Academic Misconduct

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 can get conceptual help, but you must not share, receive, request, or submit solutions from other sources, such as other students or Stack Overflow. You also may not tamper with any course infrastructure (such as hive machines and the autograder) or exploit loopholes that violate the spirit of the assignment. The word "solution" is defined as anything that may constitute an answer to a project, regardless of its correctness.

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.

For questions that includes any form of randomization (e.g. different variants for each student), you may not share the question, or anything related to the specific variant you received, with anyone else. This includes the question text, any data files provided, and your solution to the variant.

Warning: Please take a moment to review the Department Policy on Academic Misconduct. In particular, you should be aware that receiving, copying, sharing, or viewing solutions, in whole or in part, at any time, from other students in the class or any other source (including "artificial intelligence") without acknowledgement and staff approval constitutes cheating.

Here are some examples of what may be considered cheating:

  • Sharing or receiving a solution from a friend
  • Sharing or receiving a solution from a friend after the assignment is due
  • Sharing or receiving a solution from a friend after the semester is over
  • Submitting a solution from a friend to see what the autograder looks like
  • Looking at a solution that is not yours for "ideas"
  • Looking at a solution on an unattended laptop
  • Using ChatGPT or GitHub Copilot's output as your solution
  • Publicly posting your solutions for any reason, including for your resume
  • Sharing code with another student who is not your registered partner on Gradar
  • Forgetting to add your intended partner on Gradar and working with them as if you were partners anyway
  • Sharing a specific variant (including numbers and any associated files) of a randomized question
  • Working with a partner on an assignment that allows partners asynchronously

When in doubt, please reach out to staff first.

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, please let us know! We are here to support you.


For assignments that allow partners, you may collaborate with an officially registered partner, but all work must be completed synchronously. The only time where you are allowed to work on a project asynchronously with a partner is within office hours. Collaboration policies still apply outside of your partnership. For example, you can collaborate on code with your partner, but not with anyone else.

Assignments that allow partners will specify how you can officially record your partner. This is typically done through Gradar, when you get your code repository. We do not recognize partnerships created elsewhere, including Gradescope partnerships.

Warning: You and your partner are both responsible for the work your repository contains and the work you submit. If your partner cheats, you are also liable for their actions, since all work should have been done synchronously.

Cheating Detection

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:

  1. won't work, and
  2. 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. For example, if an assignment is worth 10 points, you will receive -10/10 points on the assignment, regardless of your original score. 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.

Submitting Work from Past Semesters

If you have completed assignments during past semesters and would like to reuse your work, you do not have to let staff know ahead of time. However:

  • We cannot promise that the assignments are identical across semesters.
  • If you would like to submit a project using work from past semesters, you cannot have a project partner this semester. If you had a project partner while working on your project originally, you may submit the portions of the projects that they completed.
  • By submitting work from past semesters, in part or in whole, you are claiming that the work submitted is completed entirely by you (and if applicable, your former project partner). If you are unsure if the work is your (and if applicable, your former project partner's) original work, we'd recommend redoing the assignment from scratch.

Lateness and Accommodations Policy

The expected deadlines for each assignment are posted on the class website. Our assumption is that you will complete each assignment by its due date. The course content builds on itself, and not completing an assignment will make it much more difficult to complete later assignments and do well on exams.

Lateness Policy

For homework, labs, or projects submitted late, 1/3 of your points will be deducted for each day that it's late. 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.

However, we recognize that life can be unexpected. We've accommodated some flexibility in our lateness policies, as below.

Slip Days

Each student will start with 15 slip days. Slip days can be applied to homeworks, labs, and projects. Each slip day extends an assignment deadline by one day. For homeworks and labs, at most one slip day can be applied per assignment. For projects, at most two slip days can be applied per assignment. If you apply slip days toward a partnered assignment, only you will have the extended deadline. If your partner would also like to apply slip days, they need to submit their own request.

Slip days are meant to be used for illness, submission issues and other unforeseen circumstances. Use them wisely!

Slip days can be applied on Gradar. Extended deadlines will not be reflected on Gradescope or PrairieLearn.

Important: We usually provide increased support for a particular assignment (in the form of increased staffing) leading up to the posted, original assignment deadline. As a result, continuing to work on an assignment after the original deadline may lead to slower response times on Ed/longer wait times in OH. Staff will actively prioritize assignments whose deadlines have not passed.

Extenuating Circumstances

We define extenuating circumstances as circumstances outside of the student’s control that directly inhibits the student’s ability to complete assignments in a timely manner. Some examples include unforeseen physical/mental health crises, technical issues (broken laptop), family emergency, etc. If you encounter extenuating circumstances at any time in the semester, please don’t hesitate to let us know ASAP. The sooner we are made aware, the more options we have available to us to help you.

If you are experiencing such circumstances and require an increase in the slip day limit (one day for homeworks and labs, two days for projects), or have run out of slip days and have extenuating circumstances that cover the usage of all allocated slip days, please fill out this form. This is separate from applying slip days and is a more involved process. We will be more restrictive when granting increases in the slip day limit for extenuating circumstances. We encourage you to be proactive and reach out to staff if you have prolonged extenuating circumstances that you anticipate will result in running out of slip days.

Last Day to Submit Assignments

All work must be submitted by August 11th, 11:59 PM PT. We will not accept further assignment submissions beyond this point in order to ensure that we can get grades out on time. Slip days applied beyond this date will not be considered.

Course Climate 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.

We are committed to creating a learning environment welcoming of all students that supports a diversity of thoughts, perspectives and experiences and respects your identities and backgrounds (including race, ethnicity, nationality, gender identity, socioeconomic class, sexual orientation, language, religion, ability, and more.) To help accomplish this:

  • If your name and/or pronouns differ from those that appear in your official records, please let us know.
  • 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 you feel like your performance in the class is being affected by your experiences outside of class (e.g., family matters, current events), please don’t hesitate to come and talk with us. We want to be resources for you.

Professionalism and respect for diversity are not just matters between students; they also apply to how the course staff treat the students. The staff of this course will treat you in a way that respects our differences. However, despite our best efforts, we might slip up, hopefully inadvertently. We (like many people) are still in the process of learning about diverse perspectives and identities. If you are concerned about classroom environment issues created by the overall class dynamic or by the staff, please feel free to talk to us about it.

If something was said in class (by anyone—staff member or fellow student) that made you feel uncomfortable, please talk to us about it. Sometimes, you may not be comfortable bringing this up directly to us. Here are some options:

Campus Resources

Your mental health is more important than this course. Seriously. UC Berkeley offers services to assist you with addressing mental health concerns or stressful events.

If you're in need of laptops, Wi-Fi hotspots, or other required technologies, check out the Student Technology Equity Program.

CS 61C Course Support: If you’re experiencing extenuating circumstances impacting your mental health and would like to meet with a member of course staff to work out accommodations within the course, or would like to be connected to more resources, fill out our Extenuating Circumstances form.


Portions of this policies page are derived from CS 61B's Spring 2024 policies page.