From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [Q] Looking for an emulation for CMOV* instructions.
Date: 12 Apr 2002 13:48:53 -0700 [thread overview]
Message-ID: <a97h7l$5jp$1@cesium.transmeta.com> (raw)
In-Reply-To: <m26669olcu.fsf@goliath.csn.tu-chemnitz.de> <E16Oocq-0005tX-00@the-village.bc.nu> <20020112062735.D511@toy.ucw.cz>
Followup to: <20020112062735.D511@toy.ucw.cz>
By author: Pavel Machek <pavel@suse.cz>
In newsgroup: linux.dev.kernel
>
> HI!
>
> > > 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.
>
> How long does it take until netscape binaries contain CMOV? We already do
> FPU emulation (you can do soft-float, so you do NOT need FP emulation!), so
> I guess this would begood freature.
>
The difference is that the overhead of doing FP emulation is
acceptable when compared to softfloat; this is not the case for CMOV
unless you can somehow patch the binary on the fly.
At some point it might make sense to run "the one program" that you
otherwise can't live without, but I don't think it's gotten to that
stage yet. Which is, in some ways, unfortunate.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com>
next prev parent reply other threads:[~2002-04-12 20:49 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 23:08 [Q] Looking for an emulation for CMOV* instructions 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
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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='a97h7l$5jp$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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