Re: [Q] Looking for an emulation for CMOV* instructions.

[Alan Cox]

> 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?

It means the compiler for -m686 shouldn't have assumed cmov was available

> > 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

It can be easily caught. Thats what rpm is for. If it let you install that
package on a box that can run it without using --force type options its
a bug. 

> be easy, I dunno, but the infrastructure for emulation of instructions
> is already there (FPU emulation). To say its the admins fault is easy

FPU emulation should probably have been in glibc via a fault handler
but thats a historical story.

> 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.

Then while you are it you can make the kernel magically recover from rm -rf /
or rm * in /lib...