Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: daixieit

Performance Modelling - RISC-V processor

This project will require you to implement cycle-accurate simulators of a 32-bit RISC-V processor in C++ or Python. The skeleton code for the assignment is given in fi le (NYU_RV32I_6913.cpp or NYU_RV32I_6913.py).

The simulators should take in two fi les as inputs: imem.text and dmem.txt fi les

The simulator should give out the following:

● cycle by cycle state of the register fi le (RFOutput.txt)

● Cycle by cycle microarchitectural state of the machine (StateResult.txt)

● Resulting dmem data after the execution of the program (DmemResult.txt)

The imem.txt fi le is used to initialize the instruction memory and the dmem.txt fi le is used to initialize the data memory of the processor. Each line in the fi les contain a byte of data on the instruction or the data memory and both the instruction and data memory are byte addressable. This means that for a 32 bit processor, 4 lines in the imem.txt fi le makes one instruction. Both instruction and data memory are in “Big-Endian” format (the most signifi cant byte is stored in the smallest address).

The instructions to be supported by the processor are categorized into the following types:

The simulator should support the following set of instructions.

Instruction encoding:

The simulator should have the following fi ve stages in its pipeline:

● Instruction Fetch: Fetches instruction from the instruction memory using PC value as address.

● Instruction Decode/ Register Read: Decodes the instruction using the format in the table above and generates control signals and data signals after reading from the register fi le.

● Execute: Perform operations on the data as directed by the control signals.

● Load/ Store: Perform memory related operations.

● Writeback: Write the result back into the destination register. Remember that R0 in RISC-V can only contain the value 0.

Each stage must be preceded by a group of fl ip-fl ops to store the data to be passed on to the next stage in the next cycle. Each stage should contain a nop bit to represent if the stage should be inactive in the following cycle.

The simulator must be able to deal with two types of hazards.

1. RAW Hazards: RAW hazards are dealt with using either only forwarding (if possible) or, if not, using stalling + forwarding. Use EX-ID forwarding and MEM-ID forwarding appropriately.

2. Control Flow Hazards: The branch conditions are resolved in the ID/RF stage of the pipeline.

The simulator deals with branch instructions as follows:

1. Branches are always assumed to be NOT TAKEN. That is, when a beq is fetched in the IF stage, the PC is speculatively updated as PC+4.

2. Branch conditions are resolved in the ID/RF stage.

3. If the branch is determined to be not taken in the ID/RF stage (as predicted), then the pipeline proceeds without disruptions. If the branch is determined to be taken, then the speculatively fetched instruction is discarded and the nop bit is set for the ID/RR stage for the next cycle. Then the new instruction is fetched in the next cycle using the new branch PC address.

Tasks:

1) Draw the schematic for a single stage processor and fi ll in your code in the to run the simulator. (20 points)

2) Draw the schematic for a fi ve stage pipelined processor and fi ll in your code to run the simulator. The processor should be able ot take care of RAW and control hazards by stalling and forwarding. (20 points)

3) Measure and report average CPI, Total execution cycles, and Instructions per cycle for both these cores by adding performance monitors to your code. (Submit code and print results to console or a fi le.) (5 points)

4) Compare the results from both the single stage and the fi ve stage pipelined processor implementations and explain why one is better than the other. (5 points)

5) What optimizations or features can be added to improve performance? (Extra credit 1 point)

Your work will be evaluated against the 10 test cases, 3 of which will be revealed one week before the deadline. (50 points - 5 points each)

Useful References:

● More details on the full ISA specifi cation can be found at

https://riscv.org/wp-content/uploads/2019/12/riscv-spec-20191213.pdf

● bitset library for C++: https://en.cppreference.com/w/cpp/utility/bitset

● g++: https://gcc.gnu.org/onlinedocs/gcc-3.3.6/gcc/G_002b_002b-and-GCC.html

● python: https://www.python.org/downloads/