[Assignment 2] Branch Predictor (due: 11/24, 23:59:59 (KST))

[minseongg]

Implement a branch predictor.

• Read the description here.
• You're going to modify fetch.rs, decode.rs, exe.rs, bht.rs, and btb.rs.
• Make a submission file with bash scripts/make_submission.sh and then submit hw2.zip to here.
  • If the "VALID?" column is "Yes", it means you have passed the Correctness and Performance tests.
  • To get a full score, please ensure that you have also passed the Synthesis and PnR test on your development server. Grading for Synthesis and PnR test will be done offline in batches after the deadline.
• We recommend you starting this assignment after understanding how the baseline CPU implementation works.
  • Please refer to the User Guide.
  • It will be covered in the "Pipelined RISC Processor" section in the lecture.
• IMPORTANT: Only the last submission will be used for grading. Please make sure the last submission passes the testbench.
• IMPORTANT: Don't fork the hazardflow repository, It'll be public!
• IMPORTANT: If you encounter any compiler bug, please refer to https://github.com/kaist-cp/cs492-uarch/issues/53.

[minseongg]

IMPORTANT: We updated the skeleton code for CPU, please download changes in the upstream.

Changes:

• Removed Zifencei ISA from baseline CPU
• Implemented CSR with combinators
• Refactored and simplified the implementation

[minseongg]

IMPORTANT: The current HazardFlow compiler has some unimplemented features.

If you encounter any compiler bugs, please refer to the issues listed below:

• Do not use mutable variables: https://github.com/kaist-cp/cs492-uarch/issues/30
• Use clog2() function only in the const generics: https://github.com/kaist-cp/cs492-uarch/issues/33
• Do not use return statement explicitly in the end of function: https://github.com/kaist-cp/cs492-uarch/issues/33
• Use from instead of into: https://github.com/kaist-cp/cs492-uarch/issues/33

If the bug you encountered is not listed above, please open a new issue.

[minseongg]

We added the grading script for assignment 2.

You can check the result of Correctness and Performance tests with "VALID?" column in the GG.

To get a full score, please ensure that you have also passed the Synthesis and PnR test on your development server. We will do Synthesis and PnR test offline in batches after the deadline.

FYI: We checked that all the previous submissions passed the grader.

[minseongg]

IMPORTANT: Due to some holiday break, we have not been able to cover as much material as expected (we haven't started the CPU sections yet), so we have decided to extend the deadline for Assignment 2 by three weeks.

The revised due date is 11/24, 23:59:59 (KST).

Apologies to some students who began working on the assignment early due to the original deadline...

[minseongg]

IMPORTANT: We have updated the submission script to include branch_predictor/mod.rs for grading (https://github.com/kaist-cp/hazardflow/commit/9cf6d01d4eb8e479d0802356b19b3cfdbe06dd53). Please update to the latest version from the upstream.

If you have already submitted and passed the grader, you do not need to submit again.

[minseongg]

IMPORTANT: We have fixed the CPU benchmark output: https://github.com/kaist-cp/hazardflow/commit/21aba5e97bd61b65d1405891925a82ac7e74ebd3 (Related issue: https://github.com/kaist-cp/cs492-uarch/issues/57).

Please update to the latest version from the upstream. Really sorry for the confusion.

[minseongg]

IMPORTANT: We have finished grading for Assignment 2, you can check your results in the "CREDITS" section on GG.

• If your score is "1", you have passed all the tests.
• If your score is "0", it means you failed some tests.

If you have any question for the result, please contact minseong.jang@kaist.ac.kr.