On 25 Jul 02 at 14:03, Anton Altaparmakov wrote:
> At 12:44 25/07/02, Alexander Viro wrote:
> >Al, still thinking that anybody who does mkfs.<whatever> on a multi-Tb
> >device should seek professional help of the kind they don't give on l-k...
>
> Why? What is wrong with large devices/file systems? Why do we have to break
> up everything into multiple devices? Just because the kernel is "too lazy"
> to implement support for large devices? Nobody cares if 64bit code is
> 10-20% slower than 32bit code on a storage server. The storage devices are
But I care whether gcc barfs on code or not, and whether generated code
is correct or not.
I do very trivial 64bit computations in TV-Out portion of matroxfb,
but I spent two days shifting code up/down, adding temporary variables
and splitting expressions to simple ones to make code compilable at all
with gcc-2.95.4 compiling module for PIII kernel (Debian bug #151196).
So I personally cannot recommend doing any 64bit math without setting
gcc-3.0 as minimal version for ia32 architecture.
Petr Vandrovec
vandrove@vc.cvut.cz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
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 : Tue Jul 30 2002 - 14:00:20 EST