Add unit tests for bypass module

[pavelkryukov]

Please follow:

• https://github.com/MIPT-ILab/mipt-mips/wiki/Data-Bypass-and-Scoreboard
• https://github.com/MIPT-ILab/mipt-mips/wiki/Unit-Tests
• Lecture 8; Advanced Pipelining

The idea is to model pipeline in a small scale:

    DataBypass db( 7);
    MIPS32Instr load( "ld");
    load->dst = MIPSRegister::from_cpu_index( 1);
    MIPS32Instr add( "add");
    add->src = MIPSRegister::from_cpu_index( 1);
    db.trace_new_instr( load);
    db.update(); // Go to next cycle
    CHECK( db.is_stall( add) ); // Add should have a data hazard

[bova-ev]

Do I have to test data_bypass_interface.h as well?

[pavelkryukov]

Disclaimer: you have 10 points already in this term. Any additional work will not affect your final result.

[pavelkryukov]

class RegisterState is trivial, we'll re-write it as a simple data structure later,
class BypassCommand may be tested

[bova-ev]

Ok. How do I add new unit_test to the project?

[pavelkryukov]

Add the name of the file to that list:

mipt-mips/simulator/CMakeLists.txt

Lines 59 to 82 in 5fb85fc

	set(TESTS_CPPS
	infra/t/unit_test.cpp
	infra/cache/t/unit_test.cpp
	infra/config/t/unit_test.cpp
	infra/instrcache/t/unit_test.cpp
	infra/replacement/t/unit_test.cpp
	infra/ports/port_queue/t/unit_test.cpp
	infra/ports/t/unit_test.cpp
	infra/ports/t/example_test.cpp
	kernel/t/unit_test.cpp
	kernel/mars/t/unit_test.cpp
	memory/cen64/t/unit_test.cpp
	memory/t/check_coherency.cpp
	memory/t/unit_test.cpp
	mips/mips_register/t/unit_test.cpp
	mips/t/unit_test.cpp
	func_sim/rf/t/unit_test.cpp
	risc_v/riscv_register/t/unit_test.cpp
	risc_v/t/unit_test.cpp
	risc_v/t/riscv64_test.cpp
	modules/fetch/bpu/t/unit_test.cpp
	func_sim/t/unit_test.cpp
	modules/core/t/unit_test.cpp
	export/gdb/t/unit_test.cpp

[bova-ev]

I’ve spent a lot of time figuring out what FuncInstr in DataBypass template stands for and I still couldn’t find the answer. The question is how to create an object of this class so it’ll have correct FuncInstr? All my attempts of filling this field led me to the conflict with missing methods.

[pavelkryukov]

You may use RISC-V instruction

DataBypass<RISCVInstr<uint64>> bypass;

or create a dummy instruction

struct DummyInstr
{
    // necessary methods and type definitions
};
DataBypass<DummyInstr> bypass;

[bova-ev]

Unfortunately, I'm not able to finish this issue until this night due to studies. My apologies.

[pavelkryukov]

Thank you for notification.