Tips on homework assignments

[jirheee]

Dear students,

As your Teaching Assistant, I would like to draw your attention to the closed issues in our course repository. These issues contain valuable questions, tips, and debates that previous students have created, which can be useful in helping you grasp the concepts and understand the things to watch out for.

However, since there are numerous issues, we have curated a list of issues that we believe are essential for you to read before implementing your homework assignments. Please take the time to go through these selected issues carefully, as they will provide you with a deeper understanding of the course material and help you avoid common mistakes.

hw1

• [Hw1 Question] How do we find out what nodes are in the AST? #23

hw2

• [Homework 2] If you have a problem to understand GetElementPtr Instruction, please refer to this issue #78
• [Homework 2] Tips on arithmetic operators #106
• [Homework 2] High-level Explanation about Struct #256
• [HW2] What is the result type of comparison operation? #384

hw3

• [HW3] Getting rid of the unsafe Rust #315

hw4

• [HW4] Question about joins #183

hw5

• [Homework 5] GVN algorithm in the slide: when some of the phinode arguments are constant #241

hw7 & 8

• ABI related:
  • While implementing hw7, you don't have to care about the ABI but if you plan to do hw8, we recommend reading below before implementing hw7
  • [Homework 7] Floating point calling convention. #209
• stack allocation
  • [HW7] Stack Pointer Allocation #211
  • sp byte alignment: [HW8] gg submission fails without error message again #450 (comment)
• hw8 performance - unaligned memory access
  • https://github.com/westerndigitalcorporation/RISC-V-Linux/blob/master/linux/Documentation/unaligned-memory-access.txt
• HI, LO Register
  • la instead of HI, LO: [Final Project] Performance Competition (substituting final exam, due: 8th of July) #168 (comment)

Misc

• O1 optimization
  • [Question] Is there any ir* examples after deadcode elimination pass? #406
  • [HW] Debugging test_examples_optimize #410
• Running kecc in local machine
  • [HW2]Suggestion for who is running KECC on their local machine. #314
  • [TIP] Using fuzzer with docker environment #460
• kecc ir syntax highlighter(supports vscode, vim)
  • [TIP] VSCode syntax highlighter development for KECC-IR #403
• Generating documentation
  • https://github.com/kaist-cp/kecc-public#documentation

[AnHaechan]

Added #384 to tips for hw2.