Some quick testing shows that splitting the x86 condition code register
up adds about an 8% penalty on twolf simple atomic, relative to a
version of gem5 with some performance improvements that aren't checked
in yet. That's ok since this is something that needs to happen, but that
shows the overhead of reading the extra registers. Avoiding reading any
unnecessary registers (including the zero register as a
placeholder/substitute) will help recover that lost performance.

Gabe
_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev

Reply via email to