On Sun, 2002-09-22 at 23:41, Andrew Morton wrote:
> Try gcc-2.91.66. It might break the 45 second mark.
> > IO Full Load:
> > Kernel Time CPU
> > 2.5.38 170.21 42%
> > 2.5.38-gcc32 1405.25 8%
> The streaming write is stalling gcc's read for long enough for gcc's
> working set to be evicted. And the working set cannot be reestablished
> because the streaming write prevents it. Meltdown.
> I have fixed this. Hang around.
Ehh, I was under the impression he was benchmarking kernels compiled
WITH these compilers, using contest?
Your post seems to imply he was using the compilers as the benchmark.
If so, I retract my previous post - I know gcc 3.x is slow as puke. I
think, however, he is comparing the resulting kernels, in which case
there is a serious issue at hand...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Sep 23 2002 - 22:00:38 EST