CSE2003S09.CSE2003S09 History

Hide minor edits - Show changes to markup

April 29, 2010, at 07:54 AM by 221.147.185.83 -
April 29, 2010, at 07:54 AM by 221.147.185.83 -
Changed line 5 from:
  • (2009/6/23) Your final exam score is available now. The average score is 94.2/300 (= 31.4/100). Please drop by my office by June 26 (Friday) if you want to make a claim. (I'll be out of office on Wednesday. Please send me a mail if you are going to visit my office.)
to:
  • (2009/6/23) Your final exam score is available now. The average score is 94.2/300 (= 31.4/100). Please drop by my office by June 26 (Friday) if you want to make a claim. (I'll be out of office on Wednesday. Please send me a mail and make an appointment before you visit my office.)
Changed line 5 from:
  • (2009/6/23) Your final exam score is available now. The average score is 94.2/300 (= 31.4/100). Please drop by my office by June 26 (Friday) if you want to make a claim.
to:
  • (2009/6/23) Your final exam score is available now. The average score is 94.2/300 (= 31.4/100). Please drop by my office by June 26 (Friday) if you want to make a claim. (I'll be out of office on Wednesday. Please send me a mail if you are going to visit my office.)
Added lines 4-13:
Changed line 8 from:
to:
Changed line 8 from:
to:
Changed line 8 from:
to:
Changed line 8 from:
to:
Changed lines 5-7 from:
  • (2009/6/11) PA#2 and PA#4 scores are available now. Any claim on PA#2 and PA#4 should be directed to 임이진 조교 (yjim @ hit . skku . edu) by June 18. If you forget your codename, please send me a mail. Scores of PA#1 and PA#3 will be also available soon.
to:
  • (2009/6/15) Finally, all the scores of programming assignments have been gathered. You can claim your score by June 18 (Thursday). If you forget your codename, please send me a mail.
    • Questions/Claims on PA#1 and PA#3: 윤광호 조교 (yoonkh2000 @ gmail . com)
    • Questions/Claims on PA#2 and PA#4: 임이진 조교 (yjim @ hit . skku . edu)
Changed line 5 from:
  • (2009/6/11) PA#2 and PA#4 scores are available now. Any claim on PA#2 and PA#4 should be directed to 임이진 조교 (yjim @ hit . skku . edu) by June 18. If you forget your codename, please send me a mail.
to:
  • (2009/6/11) PA#2 and PA#4 scores are available now. Any claim on PA#2 and PA#4 should be directed to 임이진 조교 (yjim @ hit . skku . edu) by June 18. If you forget your codename, please send me a mail. Scores of PA#1 and PA#3 will be also available soon.
Changed line 5 from:
  • (2009/6/11) Hello!
to:
  • (2009/6/11) PA#2 and PA#4 scores are available now. Any claim on PA#2 and PA#4 should be directed to 임이진 조교 (yjim @ hit . skku . edu) by June 18. If you forget your codename, please send me a mail.
Changed line 34 from:
  • (2009/5/4) The seatching chart for May and June is available here.
to:
  • (2009/5/4) The seating chart for May and June is available here.
Deleted line 4:
Changed line 11 from:

http://csl.skku.edu/uploads/CSE2003S09/PAScore.jpg

to:

http://csl.skku.edu/uploads/CSE2003S09/PAScore.jpg

Deleted line 12:
Changed line 12 from:

Hello!

to:

http://csl.skku.edu/uploads/CSE2003S09/PAScore.jpg

Changed line 5 from:
to:
Added line 5:
Added line 14:
Changed lines 5-6 from:
to:
Changed lines 5-6 from:
to:
Added lines 4-13:
Changed line 52 from:
  • (2009/3/4) The lecture room has temporarily changed to Semiconductor Bldg. #330110 due to the problem in the facility of the original room. I was told that it would take two or three weeks to get it fixed. Meanwhile, we will have our classes in #330110. x
to:
  • (2009/3/4) The lecture room has temporarily changed to Semiconductor Bldg. #330110 due to the problem in the facility of the original room. I was told that it would take two or three weeks to get it fixed. Meanwhile, we will have our classes in #330110.
Changed line 52 from:
  • (2009/3/4) The lecture room has temporarily changed to Semiconductor Bldg. #330110 due to the problem in the facility of the original room. I was told that it would take two or three weeks to get it fixed. Meanwhile, we will have our classes in #330110. x
to:
  • (2009/3/4) The lecture room has temporarily changed to Semiconductor Bldg. #330110 due to the problem in the facility of the original room. I was told that it would take two or three weeks to get it fixed. Meanwhile, we will have our classes in #330110. x
Changed line 52 from:
  • (2009/3/4) The lecture room has temporarily changed to Semiconductor Bldg. #330110 due to the problem in the facility of the original room. I was told that it would take two or three weeks to get it fixed. Meanwhile, we will have our classes in #330110. x
to:
  • (2009/3/4) The lecture room has temporarily changed to Semiconductor Bldg. #330110 due to the problem in the facility of the original room. I was told that it would take two or three weeks to get it fixed. Meanwhile, we will have our classes in #330110. x
Changed line 52 from:
  • (2009/3/4) The lecture room has temporarily changed to Semiconductor Bldg. #330110 due to the problem in the facility of the original room. I was told that it would take two or three weeks to get it fixed. Meanwhile, we will have our classes in #330110.
to:
  • (2009/3/4) The lecture room has temporarily changed to Semiconductor Bldg. #330110 due to the problem in the facility of the original room. I was told that it would take two or three weeks to get it fixed. Meanwhile, we will have our classes in #330110. x
Changed lines 5-6 from:
  • When: 15:00 - 17:00, June 17 (Wed), 2009.
  • Where: Semiconductor building #330110 (same as the lecture room)
to:
  • Time: 15:00 - 17:00, June 17 (Wed), 2009.
  • Location: Semiconductor building #330110 (same as the lecture room)
Changed line 4 from:
  • (2009/6/8) Final Exam Notice:
to:
  • (2009/6/8) Final Exam Notice:
Changed line 9 from:
  • (2009/6/1) We are going to have the final exam on June 15 (Monday) from 12:00 to 14:00. Well, it seems that we have no choice other than having the final exam on June 17 (Wednesday) from 15:00 to 17:00 due to the schedule of teaching assistants. Sorry for the confusion.
to:
  • (2009/6/1) We are going to have the final exam on June 15 (Monday) from 12:00 to 14:00. Well, it seems that we have no choice other than having the final exam on June 17 (Wednesday) from 15:00 to 17:00 due to the schedule of teaching assistants. Sorry for the confusion.
Changed line 5 from:
  • When: 15:00 - 17:00, June 17, 2009 (Wednesday)
to:
  • When: 15:00 - 17:00, June 17 (Wed), 2009.
Changed line 4 from:
  • (2009/6/8) Final exam:
to:
  • (2009/6/8) Final Exam Notice:
Changed lines 4-5 from:
  • (2009/6/1) We are going to have the final exam on June 15 (Monday) from 12:00 to 14:00. Well, it seems that we have no choice other than having the final exam on June 17 (Wednesday) from 15:00 to 17:00 due to the schedule of teaching assistants. Sorry for the confusion.
to:
  • (2009/6/8) Final exam:
    • When: 15:00 - 17:00, June 17, 2009 (Wednesday)
    • Where: Semiconductor building #330110 (same as the lecture room)
Added lines 8-9:
  • (2009/6/1) We are going to have the final exam on June 15 (Monday) from 12:00 to 14:00. Well, it seems that we have no choice other than having the final exam on June 17 (Wednesday) from 15:00 to 17:00 due to the schedule of teaching assistants. Sorry for the confusion.
Changed line 6 from:
  • Scope: Chap. 1, 2, 3 (except 3.14), 4.1, 4.4, 6, 7, 8.1 - 8.3, 10.1 - 10.6 + lecture slides
to:
  • Scope: Chap. 1, 2, 3 (except 3.14), 4.1, 4.4, 6, 7, 8.1 - 8.3, 10.1 - 10.6, lecture slides
Changed line 6 from:
  • Scope: everything
to:
  • Scope: Chap. 1, 2, 3 (except 3.14), 4.1, 4.4, 6, 7, 8.1 - 8.3, 10.1 - 10.6 + lecture slides
Changed line 5 from:
  • (2009/6/1) We are going to have the final exam on June 15 (Monday) from 12:00 to 14:00. Well, it seems that we have no choice other than having the final exam on June 17 (Wednesday) from 15:00 to 17:00. Sorry for the confusion.
to:
  • (2009/6/1) We are going to have the final exam on June 15 (Monday) from 12:00 to 14:00. Well, it seems that we have no choice other than having the final exam on June 17 (Wednesday) from 15:00 to 17:00 due to the schedule of teaching assistants. Sorry for the confusion.
Changed line 5 from:
  • (2009/6/1) We are going to have the final exam on June 15 (Monday) from 12:00 to 14:00. Well, it seems that we have no choice other than having the final exam on June 17 (Wednesday) from 15:00 to 17:00. Sorry for the confusion.
to:
  • (2009/6/1) We are going to have the final exam on June 15 (Monday) from 12:00 to 14:00. Well, it seems that we have no choice other than having the final exam on June 17 (Wednesday) from 15:00 to 17:00. Sorry for the confusion.
Changed line 5 from:
  • (2009/6/1) We are going to have the final exam on June 15 (Monday) from 12:00 to 14:00.
to:
  • (2009/6/1) We are going to have the final exam on June 15 (Monday) from 12:00 to 14:00. Well, it seems that we have no choice other than having the final exam on June 17 (Wednesday) from 15:00 to 17:00. Sorry for the confusion.
Added line 6:
  • Scope: everything
Changed line 5 from:
  • (2009/6/1) We are going to have the final exam on June 15 (Monday) from 12:00pm - 2:00pm.
to:
  • (2009/6/1) We are going to have the final exam on June 15 (Monday) from 12:00 to 14:00.
Added lines 4-10:
  • (2009/6/1) We are going to have the final exam on June 15 (Monday) from 12:00pm - 2:00pm.
  • (2009/6/1) The following is the final grading policy:
    • Class attendance: 10%
    • Exams: 55% (Mid 25%, Final 30%)
    • Projects: 35% (PA#1 10%, PA#2 5%, PA#3 10%, PA#4 10%)
Added lines 4-5:
  • (2009/5/27) The final programming assignment has been posted here.
Changed line 5 from:
to:
Added lines 4-5:
Changed line 5 from:
  • (2009/5/4) The Wednesday class (5/6) has been cancelled due to 예비군훈련.
to:
  • (2009/5/4) The Wednesday class (5/6) has been cancelled.
Added lines 4-5:
  • (2009/5/4) The Wednesday class (5/6) has been cancelled due to 예비군훈련.
Added lines 4-5:
  • (2009/5/4) Check out your midterm exam score in GLS. Note that the average score is 147.5/250 (= 59/100). If you want to claim your score, please drop by my office by May 11.
Added lines 4-5:
  • (2009/5/4) The seatching chart for May and June is available here.
Changed line 7 from:
  • If you don't take an exam, you will fail this course (grade F)
to:
  • If you don't take an exam, you will fail this course (grade F).
Added line 7:
  • If you don't take an exam, you will fail this course (grade F)
Changed line 5 from:
  • (2009/4/8) We will have the midterm exam on April 22 (Fri) from 15:00 to 16:20.
to:
  • (2009/4/8) We will have the midterm exam on April 22 (Wed) from 15:00 to 16:20.
Added lines 4-8:
  • (2009/4/8) We will have the midterm exam on April 22 (Fri) from 15:00 to 16:20.
    • Scope: Chapter 1 - Chapter 3.7
  • (2009/4/8) The second programming assignment is posted here.
Changed lines 5-7 from:
  • (2009/3/27) Please make sure you send your assignment not only to my address but also to the gmail account (cse2003skku at gmail dot com).
to:
  • (2009/4/1) The new seating chart for April has been posted here.
  • (2009/3/27) Please make sure you send your assignment not only to my address but also to the gmail account (cse2003skku at gmail dot com).
Added lines 4-5:
  • (2009/3/27) Please make sure you send your assignment not only to my address but also to the gmail account (cse2003skku at gmail dot com).
Changed line 5 from:
  • (2009/3/23) You can download the latest Microsoft Visual C++ 2008 Express Edition here. Thank 이태훈 for letting us this information.
to:
  • (2009/3/23) You can download the latest Microsoft Visual C++ 2008 Express Edition here. Thank 이태훈 for letting us know this information.
Changed line 5 from:
  • (2009/3/23) You can download the latest Microsoft Visual C++ 2008 Expression Edition here. Thank 이태훈 for letting us this information.
to:
  • (2009/3/23) You can download the latest Microsoft Visual C++ 2008 Express Edition here. Thank 이태훈 for letting us this information.
Changed line 5 from:
  • (2009/3/23) You can download Microsoft Visual C++ 2008 Expression Edition here. Thank 이태훈 for letting us this information.
to:
  • (2009/3/23) You can download the latest Microsoft Visual C++ 2008 Expression Edition here. Thank 이태훈 for letting us this information.
Added lines 4-5:
  • (2009/3/23) You can download Microsoft Visual C++ 2008 Expression Edition here. Thank 이태훈 for letting us this information.
Added lines 4-5:
  • (2009/3/22) Several people asked me whether it was allowed to use the unsigned int type inside mult32bits(). My answer is: Yes, you can use unsigned int-type variables in the multi32bits() function.
Changed line 5 from:
  • (2009/3/19) I was told that the long long type is not supported in Visual Studio 6.0. Since the long long type is not used inside mult32bits(), you can still implement multi32bits() with Visual Studio 6.0. However, if you want to make sure whether your result is correct or not, I recommend you to write your program in the Linux platform (or with the higher version of Visual Studio). Also, there was a little typo in the sample code included in the document for the programming assignment #1. I have uploaded a revised document. Thank Mr. 최종은 for this valuable information.
to:
  • (2009/3/19) I was told that the long long type is not supported in Visual Studio 6.0. Since the long long type is not used inside mult32bits(), you can still implement multi32bits() with Visual Studio 6.0. However, if you want to make sure whether your result is correct or not, I recommend you to write your program in the Linux platform or with the higher version of Visual Studio. Also, there was a little typo in the sample code included in the document for the programming assignment #1. I have uploaded a revised document. Thank Mr. 최종은 for this valuable information.
Changed line 5 from:
  • (2009/3/19) I was told that the long long type is not supported in Visual Studio 6.0. Since the long long type is not used inside mult32bits(), you can still implement multi32bits() with Visual Studio 6.0. However, if you want to make sure whether your result is correct or not, I recommend you to write your program in the Linux platform. Also, there was a little typo in the sample code included in the document for the programming assignment #1. I have uploaded a revised document. Thank Mr. 최종은 for this valuable information.
to:
  • (2009/3/19) I was told that the long long type is not supported in Visual Studio 6.0. Since the long long type is not used inside mult32bits(), you can still implement multi32bits() with Visual Studio 6.0. However, if you want to make sure whether your result is correct or not, I recommend you to write your program in the Linux platform (or with the higher version of Visual Studio). Also, there was a little typo in the sample code included in the document for the programming assignment #1. I have uploaded a revised document. Thank Mr. 최종은 for this valuable information.
Changed line 5 from:
  • (2009/3/19) I was told that the long long type is not supported in Visual Studio 6.0. Since the long long type is not used inside mult32bits(), you can still implement multi32bits() with Visual Studio 6.0. However, if you want to make sure whether your result is correct or not, I recommend you to write your program in the Linux platform. Also, there was a little typo in the sample code included in the document for the programming assignment #1. I have uploaded a revised document. Thanks Mr. 최종은 for this valuable information.
to:
  • (2009/3/19) I was told that the long long type is not supported in Visual Studio 6.0. Since the long long type is not used inside mult32bits(), you can still implement multi32bits() with Visual Studio 6.0. However, if you want to make sure whether your result is correct or not, I recommend you to write your program in the Linux platform. Also, there was a little typo in the sample code included in the document for the programming assignment #1. I have uploaded a revised document. Thank Mr. 최종은 for this valuable information.
Changed line 5 from:
  • (2009/3/19) I was told that the long long type is not supported in Visual Studio 6.0. Since the long long type is not used inside mult32bits(), you can still implement multi32bits() with Visual Studio 6.0. However, if you want to make sure whether your result is correct or not, I recommend you to write your program in the Linux platform. Also, there was a little typo in the sample code included in the document. I have uploaded a revised document. Thanks Mr. 최종은 for this valuable information.
to:
  • (2009/3/19) I was told that the long long type is not supported in Visual Studio 6.0. Since the long long type is not used inside mult32bits(), you can still implement multi32bits() with Visual Studio 6.0. However, if you want to make sure whether your result is correct or not, I recommend you to write your program in the Linux platform. Also, there was a little typo in the sample code included in the document for the programming assignment #1. I have uploaded a revised document. Thanks Mr. 최종은 for this valuable information.
Changed line 5 from:
  • (2009/3/19) I was told that the long long type is not supported in Visual Studio 6.0. Since the long long type is not used inside mult32bits(), you can still implement multi32bits() with Visual Studio. However, if you want to make sure whether your result is correct or not, I recommend you to write your program in the Linux platform. Also, there was a little typo in the sample code included in the document. I have uploaded a revised document. Thanks Mr. 최종은 for this valuable information.
to:
  • (2009/3/19) I was told that the long long type is not supported in Visual Studio 6.0. Since the long long type is not used inside mult32bits(), you can still implement multi32bits() with Visual Studio 6.0. However, if you want to make sure whether your result is correct or not, I recommend you to write your program in the Linux platform. Also, there was a little typo in the sample code included in the document. I have uploaded a revised document. Thanks Mr. 최종은 for this valuable information.
Changed line 5 from:
  • (2009/3/19) I was told that the long long type is not supported in Visual Studio 6.0. Since the long long type is not used inside the mult32bits() function, you can still implement multi32bits() with Visual Studio. However, if you want to make sure whether your result is correct or not, I recommend you to write your program in the Linux platform. Also, there was a little typo in the sample code included in the document. I have uploaded a revised document. Thanks Mr. 최종은 for this valuable information.
to:
  • (2009/3/19) I was told that the long long type is not supported in Visual Studio 6.0. Since the long long type is not used inside mult32bits(), you can still implement multi32bits() with Visual Studio. However, if you want to make sure whether your result is correct or not, I recommend you to write your program in the Linux platform. Also, there was a little typo in the sample code included in the document. I have uploaded a revised document. Thanks Mr. 최종은 for this valuable information.
Changed line 5 from:
  • (2009/3/19) I was told that the long long type is not supported in Visual Studio 6.0. Since the long long type is not used inside the mult32bits() function, you can still implement multi32bits() with Visual Studio. However, if you want to make sure whether your result is correct or not, I recommend you to write your program in the Linux platform. Also, there was a little typo in the sample code for the programming assignment #1. I have uploaded a revised document. Thanks 최종은 for this valuable information.
to:
  • (2009/3/19) I was told that the long long type is not supported in Visual Studio 6.0. Since the long long type is not used inside the mult32bits() function, you can still implement multi32bits() with Visual Studio. However, if you want to make sure whether your result is correct or not, I recommend you to write your program in the Linux platform. Also, there was a little typo in the sample code included in the document. I have uploaded a revised document. Thanks Mr. 최종은 for this valuable information.
Added lines 4-5:
  • (2009/3/19) I was told that the long long type is not supported in Visual Studio 6.0. Since the long long type is not used inside the mult32bits() function, you can still implement multi32bits() with Visual Studio. However, if you want to make sure whether your result is correct or not, I recommend you to write your program in the Linux platform. Also, there was a little typo in the sample code for the programming assignment #1. I have uploaded a revised document. Thanks 최종은 for this valuable information.
Added lines 4-5:
  • (2009/3/18) The first programming assignment is posted here. Good luck!
Added lines 4-5:
  • (2009/3/18) Since you will need access to a Linux system for most of programming assignments, I have summarized how you can run Linux on top of your Windows-based PC. Please check out the Resources page for further details.
Added lines 4-5:
  • (2009/3/11) We will continue to have our classes in the lecture room #330110 throughout this semester.
Changed line 5 from:
to:
Added lines 4-5:
Changed line 5 from:
  • (2009/3/4) The seating chart for March has been posted here. If your name is incorrectly placed or missing in the chart, please send me a mail or see me after the class.
to:
  • (2009/3/4) The seating chart for March has been posted here. If your name is misplaced or missing in the chart, please send me a mail or see me after the class.
Changed line 7 from:
  • (2009/3/4) The lecture room has temporarily changed to Semiconductor Bldg. #330110 due to the problem in the facility of the original room. I was told that it would take two or three weeks to get it fixed. Meanwhile, we will have our class in #330110.
to:
  • (2009/3/4) The lecture room has temporarily changed to Semiconductor Bldg. #330110 due to the problem in the facility of the original room. I was told that it would take two or three weeks to get it fixed. Meanwhile, we will have our classes in #330110.
Changed line 7 from:
  • (2009/3/4) The lecture room has temporarily changed to Semiconductor Bldg. #330110 due to the problem in the facility in the original room. I was told that it would take two or three weeks to get it fixed. Meanwhile, we will have our class in #330110.
to:
  • (2009/3/4) The lecture room has temporarily changed to Semiconductor Bldg. #330110 due to the problem in the facility of the original room. I was told that it would take two or three weeks to get it fixed. Meanwhile, we will have our class in #330110.
Changed lines 3-42 from:
to:

[News]

  • (2009/3/4) The seating chart for March has been posted here. If your name is incorrectly placed or missing in the chart, please send me a mail or see me after the class.
  • (2009/3/4) The lecture room has temporarily changed to Semiconductor Bldg. #330110 due to the problem in the facility in the original room. I was told that it would take two or three weeks to get it fixed. Meanwhile, we will have our class in #330110.
Changed lines 11-12 from:
to:
Changed lines 11-12 from:
to:
Changed lines 11-12 from:
to:
Changed line 11 from:
to:
Changed line 26 from:
  • Intel Architectures Software Developer's Manual, Intel Corp.
to:
  • Intel Architectures Software Developer's Manuals, Intel Corp.
Changed line 16 from:
to:
Changed lines 16-17 from:
to:
Changed line 17 from:
to:
Changed line 17 from:
to:
Changed lines 8-9 from:
to:
Changed line 3 from:

General information

to:

[General information]

Changed line 32 from:
to:
Changed lines 31-33 from:
to:
Changed lines 31-32 from:
to:
Added lines 31-36:
Changed lines 18-19 from:
to:
Deleted lines 20-23:
Changed lines 22-25 from:

- C programming skills
- Basic knowledge of Unix/Linux systems
- ICE2001: Logic circuits
- ICE2002: Data structures

to:
Changed lines 18-22 from:
to:
Changed line 18 from:
to:
Added lines 17-18:
Changed lines 19-21 from:

- C programming skills - Basic knowledge of Unix/Linux systems - ICE2001: Logic circuits

to:

- C programming skills
- Basic knowledge of Unix/Linux systems
- ICE2001: Logic circuits\\

Changed lines 19-22 from:
  • C programming skills
  • Basic knowledge of Unix/Linux systems
  • ICE2001: Logic circuits
  • ICE2002: Data structures
to:

- C programming skills - Basic knowledge of Unix/Linux systems - ICE2001: Logic circuits - ICE2002: Data structures

Changed line 19 from:
* C programming skills
to:
  • C programming skills
Changed line 19 from:
* C programming skills
to:
* C programming skills
Changed line 19 from:
  • C programming skills
to:
* C programming skills
Changed lines 18-19 from:
to:
Changed lines 17-21 from:
to:
Changed line 14 from:

Computer Systems Laboratory\\

to:

Computer Systems Laboratory

Deleted lines 14-15:

http://csl.skku.edu/images/jinsoo-email2.png
Tel: 031-299-4593, Office: Semiconductor Bldg. #400630

Changed line 12 from:
to:
Added line 15:

http://csl.skku.edu/images/jinsoo-email2.png \\

Changed line 12 from:
to:
Changed line 12 from:
to:
Changed line 7 from:
to:
Changed line 6 from:
to:
Deleted line 8:
Deleted line 10:
Deleted line 15:
Changed line 6 from:
to:
Changed lines 19-20 from:
to:
Deleted lines 23-29:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim \\ (Tel: 031-299-4593, Office: Semiconductor Bldg. #400630)
 (Tel: 031-299-4593, Office: Semiconductor Bldg. #400630)
Overview:This course is an introduction to concepts underlying all computer systems. More specifically, this course provides a programmer's view of how computer systems execute application programs, store information, and communicate with each other. This course also serves as a foundation for courses on operating systems, computer architectures, compilers, programming languages, computer networks, and embedded systems, where a deeper understanding of systems-lvel issues is required. Topics covered include data representations, assembly languages, processor architectures, the memory hierarchy, operating systems, compilers, linkers and loaders, and high-lvel application programming interfaces.
Added lines 14-19:
Deleted lines 20-24:

Associate Professor Computer Systems Laboratory Tel: 031-299-4593, Office: Semiconductor Bldg. #400630

Added lines 9-19:
Added lines 4-10:
Changed line 5 from:
to:
Changed line 8 from:
Instructor:Jin-Soo Kim
to:
Instructor:Jin-Soo Kim \\ (Tel: 031-299-4593, Office: Semiconductor Bldg. #400630)
Added line 9:
 (Tel: 031-299-4593, Office: Semiconductor Bldg. #400630)
Changed line 5 from:
to:
Added lines 9-10:
Overview:This course is an introduction to concepts underlying all computer systems. More specifically, this course provides a programmer's view of how computer systems execute application programs, store information, and communicate with each other. This course also serves as a foundation for courses on operating systems, computer architectures, compilers, programming languages, computer networks, and embedded systems, where a deeper understanding of systems-lvel issues is required. Topics covered include data representations, assembly languages, processor architectures, the memory hierarchy, operating systems, compilers, linkers and loaders, and high-lvel application programming interfaces.
Changed lines 6-8 from:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
to:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
Changed line 5 from:
to:
Changed lines 6-8 from:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
to:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
Changed lines 5-8 from:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
to:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
Changed lines 6-8 from:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
to:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
Changed lines 6-8 from:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
to:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
Changed line 5 from:
to:
Changed lines 6-8 from:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
to:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
Changed lines 6-8 from:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
to:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
Changed lines 6-8 from:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
to:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
Changed lines 6-9 from:
LeftLeft
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
to:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
Changed line 6 from:
LeftLeft
to:
LeftLeft
Changed line 6 from:
!Left!Left
to:
LeftLeft
Added line 6:
!Left!Left
Added lines 5-8:
When:12:00-13:15 (Monday), 15:00 - 16:15 (Wednesday)
Where:Lecture room #26312
Instructor:Jin-Soo Kim
Changed lines 1-4 from:

CSE2003: System Programming (Spring 2009)

to:

CSE2003: System Programming (Spring 2009)

General information

Changed lines 1-2 from:

CSE2003 (Spring 2009)

to:

CSE2003: System Programming (Spring 2009)

Added lines 1-2:

CSE2003 (Spring 2009)