I'm not particularly familiar with the Minor code, but let's go for the
usual suspects. When you say 5 cycles on correctly predicted branches,
is it an average, or is it for some branches? Is it for taken or non-taken?
Could it be misses in the I-Cache/ITLB?
Le 22/11/2016 à 11:49, Will a écrit :
Hello,
I'v been trying to conduct some simulation using MinorCPU and got
confused about the timing when branch taken.
In default configuration, I found that there are about 5 clcok cycles
idle when a branch prediction is correct, while there are about 11
clcok cycles idle when a branch prediction is incorrect. To my
knowledge, if the branch prediction is correct, it must have no extra
idle cycles.
I want to know why there have extra cycles when branch taken in
default configuration and is there has some flags to eliminate the
extra cycles and make the instruction flow continuous.
I really appreciate for you help. Thanks.
Wil
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
