h44z/uibk_703602-Compiler-Construction
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update course information for next semester

Browse Source
This commit is contained in:
Alex Hirsch
2021-02-04 13:21:11 +01:00
parent 21a5b2cd61
commit 666a1860a7
4 changed files with 42 additions and 70 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
slides/intro_slides.md
View File

@@ -1,12 +1,12 @@
% Compiler Construction
% Alex Hirsch
% 3 March 2020
% 5 March 2021
# This ProSeminar
# This Proseminar
## Curriculum
> […] development of a compiler for a simple procedural programming language
> […] development of a compiler for a simple, procedural programming language
<aside class="notes">
As stated by the curriculum, your task is to build a simple compiler for a small procedural programming language.
@@ -20,16 +20,12 @@ Still, it is highly recommended to work in teams and that you start early - alwa
- This is a master's course!
- Brain
If you struggle too much, do this course at a later time.
You can unregister until the end of April.
<aside class="notes">
By now, this course is notorious for requiring a lot of effort.
The legends are true; I am indeed expecting a decent level of skill from all of you.
This is a master's course after all.
While I don't care whether you have officially finished your bachelor, you should only take this course if you are certain that you meet the prerequisites.
Otherwise, skip it for now and come back to it when you have acquired the necessary knowledge.
</aside>
- - -
@@ -50,7 +46,7 @@ Otherwise, skip it for now and come back to it when you have acquired the necess
Since this course is very programming intensive, you need to be fluent in one of these languages.
If choose C and think strings are compared using `==` you'll have a very hard time.
For OS, if you think calling `exec` without `fork` while implementing a library is a good idea, maybe revisit the corresponding lecture would be a good idea.
For OS, if you think calling `exec` without `fork` while implementing a library is a good idea, maybe revisiting the OS course would be a good idea.
</aside>
- - -
@@ -85,23 +81,13 @@ The lecture and proseminar assumes that you are familiar with the basics of gram
- Specification provided
- Evaluation scheme provided
## In the Lab
- QA sessions
- I'll be present for questions
- You can work on your compiler
## Requirements
- Working compiler
- More positive than negative QA sessions
## Recommended Schedule
- March: lexer / parser
- April: semantic checks, start IR generation
- May: finish IR generation, start ASM generation
- June: finish ASM generation, CFG generation, polish
- See README
<aside class="notes">
You are free to deviate from this schedule.