>>>>> "Matthias" == Matthias Andree <matthias.andree@gmx.de> writes:
Matthias> On Tue, 01 Aug 2000, Jes Sorensen wrote:
>> Just because it seems to compile the specific configuration you are
>> using does NOT mean it will compile everything else correctly. Is
>> that really so hard to understand?
Matthias> No, that's evident. Still, if you don't try it because
Matthias> someone (you) considers it unsupported, you won't fix
Matthias> it. Neither the kernel nor gcc.
Matthias> I have compiled every so many Gigs of source code with gcc
Matthias> 2.95.2, and the only time something broke was when AT&T's
Matthias> graphviz was nuked by LC_COLLATE=de_DE.ISO-8859-1 that had a
Matthias> different notion of how to sort spaces than LC_COLLATE=POSIX
Matthias> had.
Compiling gigs of source code doesn't probe a thing.
Matthias> Still, gcc 2.95.2 has not yet trapped me although I use -O6
Matthias> -march=pentium -mcpu=k6 on everything but the kernel, which
Matthias> sticks to whatever the Makefile considers appropriate.
I am beginning to wonder if you really know what you are doing. Do you
actually know what -O6 does? Automatically unrolling loops and
inlining functions behind your back is not necessarily something you
want on a modern CPU.
Matthias> go use 2.95.2 and see where it bombs and fix the
Matthias> offender. Heck, gcc 2.95.2 cannot be all that buggy, why
Matthias> would FreeBSD 4.x work if it was?
I use 2.96 every day and I frequently report bugs in it, on the ia64!
I do not use it on 2.2.x kernels for the x86 because of the well known
issues.
Jes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Aug 07 2000 - 21:00:13 EST