CS61C Section 23

TA: Gek Siong Low (cs61c-tb)
Lab: W 8-9 271 Soda
Discussion: F 8-9 310 Soda
Office Hours: Tue 2-330 at 5th floor Soda lounge (or by appointment)

Your reader is: Diana Yang (cs61c-re)

CS61C Class Webpage: http://www-inst.eecs.berkeley.edu/~cs61c
Class newsgroup: ucb.class.cs61c

Class pictures here


Announcements | Discussion Notes | Some useful things to know | About Me

Announcements

(4/30) Week 14 notes are up.

(4/24) For those who came to last week's discussion, I realized I was filling in the associative cache in the wrong direction, which was why it didn't make sense. The solution I have is not very clear about this part, so I'm going to try explaining it again next discussion.

(4/24) I've put up some sample final problems and solutions to them from my TA when I took the class.

(4/15) Week 12 notes are up.

(4/8) These last few topics are best learned by doing it yourself and having someone demonstrate the concepts to you. The textbook and lecture notes are full of diagrams so I won't put a lot of stuff in the notes. Also, I'll be too busy with my classes now to write really comprehensive notes. Please ask questions in class if you don't understand the concepts.

(4/8) Week 11 discussion notes are up.

(4/2) Errata: The tag should be (32-N) bits instead of (32-N-M). The notes has been changed.

(4/1) Week 10 discussion notes are up

(3/11) Tommorrow's discussion: I'll just answer questions you may have on the sample midterms.

(3/11) Oops a typo. I mean "spin-waiting" not "spim-waiting", but I'm sure all of you have already figured that out. :-)

(3/3) Week 7 discussion notes are up.

(2/26) Week 6 discussion notes are up.

(2/19) Put up some supplementary notes regarding MIPS calling conventions and a "solution" for Lab 3.

(2/16) Oops. Found some typos. They are okay now.

(2/16) Week 5 discussion notes are up. Happy Chinese New Year to all.

(2/10) Week 4 discussion notes are up.

(2/9) I've uploaded spim 4 to the class web page. Everything MIPS should be consistent now.

(2/5) Week 3 discussion notes are up.

(2/5) My office hours are now shifted to Tue 2-330 instead of Thu 2-330.

(2/5) Project 2 is online.

(2/3) Class pictures are now up, click here to see them.

(2/3) Some instructions I used for my discussion notes runs only on spim version 4. The PC versions on the class web page are version 6. I'll get this issue straightened out with the prof and other TAs soon.

(1/30) Week 2 discussion notes are up. If my ascii diagrams are too large to print, tell me and I'll see if I can make them smaller

(1/23) I've put up some notes about C programming

(1/22) The midterm is on 3/17 5pm and the final is on 5/12 5pm, please inform us if there are any conflicts so that we can make alternative arrangements

(1/22) HW1 due 1/27, please see class webpage

(1/22) Project 1 is online on class webpage

(1/22) I will try to write up some notes to put online over the weekend. Some of the other TAs have also put up online notes, you can take a look at them.

(1/22) As this is my first time TAing, I need you guys to give me comments, good or bad. If you find me boring or the discussion too easy for you, please tell me and we can do something more interesting.

(1/22)I wouldn't mind if you think another TA is better than I, and attend his section instead, but please come for the first few discussions until we get the enrollment stuff settled before you start disappearing.

(1/22) Somebody left behind a mechanical pencil in the first lab. If you can describe it, it's yours.

(1/22) Okay, this page looks terrible, I know. But I'm not going to make it look any nicer.


Discussion Notes

Week 1
Week 2
Week 3
Week 4
Week 5
Things to consider when writing a MIPS function
A "solution" to Lab 3 (used in conjunction with the MIPS conventions notes)
Week 6
Week 7
Week 8 : Sample midterm Q&A. No notes for this week.
Week 9 : Spring Break.
Week 10
Week 11
Week 12
Week 13: Here are some sample final problems which I got from my TA in CS61C Spring 1998, and the solutions. It includes the lab9/associative cache question I did class. No guarantees about the correctness/clarity of the solutions though. I didn't really go through them. Please download and print with enscript to save paper
Week 14


Some useful things to know

To print a postscript file

HPs: lpr -dlw274 filename.ps
Solaris: lp -dlw274 filename.ps

To print a pdf file

HPs: run acroread, and in the print window, use lpr -dlw274 as the command to run
Solaris: use xpdf instead. Acroread is not installed on the Solaris machines

To print any text file

enscript -2Grdlw274 filename.txt

This prints out the text file in landscape orientation, 2 pages per page and with those pretty headers that you see on printouts left lying about near the printers. The dlw274 has exactly the same meaning as for lpr.

Accessing the newsgroup from home with a news reader

You can connect only through home-ip. Set your newsgroup server to agate.berkeley.edu. You can use any news reader, whichever is your favorite.

Accessing the newsgroup without running Netscape or without using home-ip

If you a pine user (like me), you can access the newsgroups through pine. Just put the news server name in the setup, and use "Add" to add newsgroups.

Advantage: So long as you can telnet to one of the Unix machines, you can use the newsgroups on the agate server, regardless of whether you are using home-ip or not.


About Me

I'm an EECS junior (Option C). This is my first time TAing. I took this class 2 semesters ago with Mike Clancy. This is the only section I'm teaching. I write better than I speak (maybe you've noticed it). And I prefer to answer questions than to lecture, actually (no homework questions please). I prefer C++ to C, so please correct me if I start writing C++ code instead of C code.

I run Linux, use a Casio E-10, and play the classical guitar. I'll probably be going into software and taking all the 160s.

EE/CS classes I've taken: EECS120, EECS122, CS164, CS170, CS188 (you can ask me questions about theses classes)

For more about me, see below.

CS classes I'm taking now: CS169


Some advice for the class

1. If you are not already proficient in C, I suggest you go get the K&R book. Or you can always use the man pages (urgh!)

2. Keep up with the reading and do your homework!

3. Don't cheat. Especially: don't copy code or even follow the same structure. It's best to write code without looking at anybody else's code.

4. Make use of the newsgroup. They are your #1 source of help. I tend to monitor newsgroups more than I look at my email. Ask freely. I'll strike down anybody who says that you are a moron.

5. This may sound obvious, but don't post your program on the newsgroup for everybody to see! If you must have your program read through by somebody, either get a friend to debug it, or email it to us.

6. Gek's approach to learning: Step one: How? Step two: Why? Along the way: Ask!


Shameless plug

My HHGTTG page: http://www.geocities.com/Area51/Station/3690
(if you don't know what HHGTTG is, you should go and read the book)


42 - The only answer we'll ever need
-- Hitchhiker's Guide to the Galaxy

Last updated on 4/30/99 2:30 am