mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hans-Peter Jansen <hpj@urpla.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Ronald.Wahl@informatik.tu-chemnitz.de (Ronald Wahl)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Q] Looking for an emulation for CMOV* instructions.
Date: Fri, 11 Jan 2002 20:59:45 +0100	[thread overview]
Message-ID: <20020111195946.38C35142E@shrek.lisa.de> (raw)
In-Reply-To: <E16Oocq-0005tX-00@the-village.bc.nu>
In-Reply-To: <E16Oocq-0005tX-00@the-village.bc.nu>

On Friday, 11. January 2002 00:28, Alan Cox wrote:
> > is it possible to include an emulation for the CMOV* (and possible other
> > i686 instructions) for processors that dont have these (k6, pentium
> > etc.)? I think this should work like the fpu emulation. Even if its slow
>
> The kernel isnt there to fix up the fact authors can't read. Its also very
> 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.

But it shouldn't crash, if the wrong architecture is chosen. (Different
problem, I know) Perfect solution would be emulate them all, but at least
an simple error message (please eject CPU, and put in a XXX one) would be 
sufficient, IMHO. 

> If you have a static linked program install the right version. RPMv4
> even knows about cmov and i686 rpms.

Hans-Peter

  parent reply	other threads:[~2002-01-11 20:00 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-10 23:08 Ronald Wahl
2002-01-10 23:28 ` Alan Cox
2002-01-11  0:08   ` Ronald Wahl
2002-01-11  0:26     ` Alan Cox
2002-01-11  0:39       ` Ronald Wahl
2002-01-11  0:54         ` Alan Cox
2002-01-11  1:09           ` Martin Eriksson
2002-01-11  1:42             ` Timothy Covell
2002-01-11  2:16             ` Alan Cox
2002-01-11 18:24           ` Ronald Wahl
2002-01-11 22:18           ` Richard Henderson
2002-01-11 23:07             ` Alan Cox
2002-01-11 23:26               ` Albert D. Cahalan
2002-01-11 23:40                 ` Alan Cox
2002-01-16 15:18               ` Jamie Lokier
2002-01-16 16:16                 ` Richard B. Johnson
2002-01-16 17:48                   ` Ronald Wahl
2002-01-16 17:30                 ` Dave Jones
2002-01-17 11:54                 ` Maciej W. Rozycki
2002-01-11 19:59   ` Hans-Peter Jansen [this message]
2002-01-11 20:05     ` Ronald Wahl
2002-01-11 23:19       ` Alan Cox
2002-01-12  6:27   ` Pavel Machek
2002-04-12 20:48     ` H. Peter Anvin
2002-01-12  6:34   ` Pavel Machek
2002-01-18 17:38   ` David Woodhouse
2002-01-18 22:01     ` Pavel Machek
2002-01-11 23:25 ` Alistair Riddell
     [not found] <fa.eln67tv.a4io16@ifi.uio.no>
     [not found] ` <fa.gp0gofv.1p4se16@ifi.uio.no>
2002-01-11  8:12   ` Giacomo Catenazzi
2002-01-11  9:25 willy tarreau
2002-01-11 17:55 ` Ronald Wahl
     [not found] <m26669olcu.fsf@goliath.csn.tu-chemnitz.de.suse.lists.linux.kernel>
     [not found] ` <E16Oocq-0005tX-00@the-village.bc.nu.suse.lists.linux.kernel>
2002-01-11  9:54   ` Andi Kleen
2002-01-12  6:31     ` Pavel Machek
2002-01-12  7:52     ` H. Peter Anvin
     [not found] <200201111845.g0BIjS2318104@saturn.cs.uml.edu>
2002-01-12  9:00 ` willy tarreau
2002-01-12 18:57   ` Alan Cox
2002-01-12 10:48 Adam J. Richter
2002-01-12 11:25 ` David Weinehall
2002-01-12 13:18 ` Brian Gerst
2002-01-12 20:43 ` H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020111195946.38C35142E@shrek.lisa.de \
    --to=hpj@urpla.net \
    --cc=Ronald.Wahl@informatik.tu-chemnitz.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®