On Wednesday 13 April 2005 00:18, Pat Haugen wrote: > When we have a test block gating whether a loop should be > entered, the new block frequency check causes the code to pick the non-loop > path as the next block to add to the trace since the loop header block has > a higher frequency, and hence the loop gets moved out of line.
Have you tried with the patch to re-enable the loop header copying predictor: http://gcc.gnu.org/ml/gcc-patches/2005-03/msg02577.html? It sounds like you might want to try that first... Gr. Steven
