Kevin Buhr writes: > If I recall correctly, RedHat's 2.96 was a modified development > snapshot of GCC 3.0, not an official GCC release. If this is just a > quirk in 2.96 that can be fixed before the official release of 3.0 by > a trivial patch to libiberty, maybe your original hunch was right and > the kernel should be left as-is. It is the garbage collector scheme used for memory allocation in gcc >=2.96 that triggers the bad cases seen by Serge. Later, David S. Miller [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Linux 2.4.2 fails to merge mmap areas, 700% slowdown. Serge Orlov
- Re: Linux 2.4.2 fails to merge mmap areas, 700% slo... Linus Torvalds
- Re: Linux 2.4.2 fails to merge mmap areas, 700%... Jakob Østergaard
- Re: Linux 2.4.2 fails to merge mmap areas, 700%... Kevin Buhr
- Re: Linux 2.4.2 fails to merge mmap areas, ... David S. Miller
- Re: Linux 2.4.2 fails to merge mmap are... Jakob Østergaard
- Re: Linux 2.4.2 fails to merge mma... James Lewis Nance
- Re: Linux 2.4.2 fails to merge mma... Linus Torvalds
- Re: Linux 2.4.2 fails to merge... Jakob Østergaard
- Re: Linux 2.4.2 fails to merge mma... Kevin Buhr
- Re: Linux 2.4.2 fails to merge... Linus Torvalds
- Re: Linux 2.4.2 fails to m... Kevin Buhr
- Re: Linux 2.4.2 fails to merge mma... Kevin Buhr
- Re: Linux 2.4.2 fails to merge... Jakob Østergaard
- Re: Linux 2.4.2 fails to m... Jamie Lokier