UB Catalog information for CSE 220
This information is advisory only. The authoritative course description and requirements for a given semester are defined by the course syllabus.
This course is a required course in the 2018 and later curriculum. It covers low-level systems programming in userspace at the userspace/kernel boundary. Students will learn about the C programming language, system calls, memory management, threads, and concurrency.
OfferingsSpring 2019, Fall 2019, Spring 2020, Fall 2020, Spring 2021, Fall 2021, Spring 2022, Fall 2022, Spring 2023, Fall 2023
Current Offering: Fall 2023
A: MWF 13:00-13:50, Davis 101 (Ethan Blanton);
B: MWF 15:00-15:50, NSC 201 (Carl Alphonce);
C: MWF 09:00-09:50, NSC 201 (Ethan Blanton)
|Lab||A1, A2, A4-A7, B1-B6, C2-C7: Check HUB|
Mo 10:00-10:50, Davis 334 (Ethan Blanton)
Tu 08:00-09:20, Davis 343 (Carl Alphonce)
We 10:00-10:50, Davis 343 (Carl Alphonce)
|TA Office Hours||(See Piazza)|
|Introduction to CSE 220 and C (pdf)||2023-08-28|
|Variables, Strings, and Loops (pdf)||2023-08-30|
|Conditionals and Control Flow (pdf)||2023-09-08|
|A Tour of Computer Systems (pdf)||2023-09-13|
|Memory and Pointers (pdf)||2023-09-18|
|Structures and Allocation (pdf)||2023-09-25|
|Alignment, Padding, and Packing (pdf)||2023-09-29|
Students are expected to have a solid grasp of simple data structures (such as lists and arrays) and some programming experience. (CSE 116 or equivalent experience.)
There is one required text for this course:
- The C Programming Language, Second Edition, by Brian W. Kernighan and Dennis M. Ritchie.
Students will also be required to use TopHat for lecture interaction, which will be used for direct evaluation in the form of lecture quizzes, as well as attendance tracking.
There is one optional text for this course:
- Computer Systems: A Programmer’s Perspective, Third Edition, by Randal Bryant and David O’Hallaron.
Both of the listed textbooks are truly excellent, and we recommend that you consider buying a copy to keep for your career.
Unfortunately CS:APP is quite expensive (more expensive than we would expect, given the number of copies that must be sold per year!). The least expensive legitimate method we are aware of for purchasing this book is RedShelf There is a Second International Edition PDF floating around the Internet that students often pirate; be warned that it has many errors and is different from the required Third Edition text. If you are purchasing a used textbook online, try to make sure you are getting the US Edition, as the International Edition has more errors.
The ultimate authority for course policies is the course syllabus.
This course additionally adopts Ethan’s general academic integrity policy, which can be found here. His complete list of policies is here.
The topics to be covered in this course include:
- The C programming language
- Compiler and linker invocation and their roles in program development
- Version control, build, and other systems
- Representation of in-memory data structures
- Memory management
- The kernel/userspace boundary and the system call interface
- Synchronization primitives and concurrency
You can find advice for succeeding in CSE 220 here. This is likely to be one of the more difficult courses you take in your career at UB, both due to the content of the course and to the position it has in the curriculum. We understand this, and are here to support your learning. Work hard, ask questions, and get help when you need it.
This course will be conducted in-person, pending contradictory guidance from SUNY or the University at Buffalo. Students are expected to attend lectures and labs unless they have a University-approved reason to miss. Students must not attend if they have reason to believe that they may have a communicable infection or illness, with or without noticeable symptoms.
The primary deliverables for this course are weekly labs and several larger projects. Labs will consist of short exercises intended to deepen student understanding of course material (and perhaps cover background material for course projects), and will be evaluated in-lab. Course projects will be C language implementations of concepts discussed in class. Projects and labs will make up about half of the final course grade, with the remainder being quizzes and exams.
There is one midterm and one (cumulative) final for this course. These written exams cover theoretical and fundamental materials beyond the specific implementation details required for the programming assignments and labs. In-lecture activities and short quizzes will cover lecture content, lab procedures, course policies, and other important material.
There are no other graded homeworks for this course.
All projects for this course must be implemented in C and compile and run correctly on the course-provided time-sharing system. Students will be expected to use version control and appropriate build tools (such as make) to manage their projects.