System calls should flush pipeline about mipt-mips HOT 3 CLOSED

This method is private. Should I write a test?

from mipt-mips.

You must, but you cannot write a test for private method.

First of all, you should write a test that fails because of the wrong behavior. ("red stage")
Then, you fix the code so test passes and other tests are not affected. ("green stage").
Finally, you refactor and optimize code ("refactor stage").

For more details on TDD, please follow our Wiki page: https://github.com/MIPT-ILab/mipt-mips/wiki/Introduction-to-Test-Driven-Development. It's not the best manual, but you may look for lots of resources over the Internet.

For testing, there can be two approaches:

• Difficult one. You write unit tests for Writeback module from scratch: writing some instructions to input ports, reading the expected output from the output ports. It goes far beyond that issue, we even need a dedicated tracker.
• Simple one (I suggest going here). We test PerfSim as a whole system. The idea is to provide a binary input and a keyboard input which cause a error. I assume the binary input has no problem for you as it is used already (see code below), keyboard input is not so hard as well, since you may use std::istringstream as a parameter to MARSKernel class instead of std::cin.

from mipt-mips.

Now we can study microarchitecture in a much interactive manner! Congratulations!

from mipt-mips.