3 ms·
The answer can be one of a billion reasons: dependency chain breaking, register renaming deficiencies, alias breaking, etc. First step needs to be the hardware
by DannyBee 13y ago
The answer can be one of a billion reasons:
dependency chain breaking, register renaming deficiencies,
alias breaking, etc.
First step needs to be the hardware performance counters.
Usually it will tell you something interesting, but leave you scratching your head.
Then you find a friend at intel, who laughs, and explains some wildly esoteric detail of the core2 processor that causes this.
This is why scheduling and register allocation models in compilers don't bother with ILP based modeling for x86 processors. Even if you modeled the externally published architecture perfectly, including port restrictions, decode lengths, branch stalls, cycle counts, register requirements, etc, the processor just does whatever it wants internally anyway, because they don't really give you all the details.