I might have asked you this before. Do the processor designs that are out there in the market
have separate condition code register file?

src/cpu/o3/cpu.cc (Diff revision 1)

Is this #ifdef required? When NumCCRegs maps to zero, the loop is not executed.

Show all issues

src/cpu/o3/cpu.cc (Diff revision 1)

Do we use this code? From a cursory look, it seems that this code is required for context switching in SE mode. Should we not just drop all of it?

Show all issues

1. Steve Reinhardt Sept. 27, 2013, 3:51 p.m. (Sept. 27, 2013, 3:51 p.m.)

   I don't believe we use this code, and I don't believe it works properly.  What it is supposed to do is to dynamically change the number of thread contexts so that if there's only one active thread, it uses all the resources (including all the physical registers), then as you add threads you allocate from the physical register file to accommodate them.  Currently I believe that you statically set the number of threads, and then each thread gets a set of physical registers to hold its architectural registers, then they only compete for the leftover physical regs.
   
   I would not be opposed to identifying all the unused code and getting rid of it.  However, that should be done in a separate changeset.