>> > hard to get emulations right. I grant that this wasn't helped by the fact
>> > the gcc x86 folks also couldnt read the pentium pro manual correctly.
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> What do you mean with this? Explain, please!
> gcc told to generate i686 binaries uses cmov unconditionally. The intel
> PPro handbook explicitly says that cmov must be checked for.
The compiler doesn't know, where the binary runs later. Or do you mean,
that it has to insert some code that checks for the existance of these
instructions during program start? Ok that would be a solution, but how
do you do this for libraries that are not run in itself?
>> myself but I have also some older machines here that have a k6 or a
>> pentium. For mistake I installed the wrong rpm and had a non working
>> system. An emulation for such cases would be a _real_ feature at least
> So you have a buggy rpm program. Get the rpm program fixed so it correctly
> stops you from doing that.
Maybe, ok. But why should such a mistake prevent me from workin with the
system when it could be easily catched? Ok, the emulation code may not
be easy, I dunno, but the infrastructure for emulation of instructions
is already there (FPU emulation). To say its the admins fault is easy
but the costs of automatically catching such errors are little in
respect of the benefit you get. A running system is always better than
a unusable one even if it was the admins fault.
ron
-- /\/\ Dipl.-Inf. Ronald Wahl /\/\ C S N /\/\ \/\/ ronald.wahl@informatik.tu-chemnitz.de \/\/ ------------------ \/\/ /\/\ http://www.tu-chemnitz.de/~row/ /\/\ network and system /\/\ \/\/ GnuPG/PGP key available \/\/ administration \/\/ - 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/