Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!agate!e260-1e.berkeley.edu!c60b-1eq
From: c60b-1eq@e260-1e.berkeley.edu (Noam Mendelson)
Newsgroups: comp.sys.ibm.pc.hardware
Subject: Re: C64 emulation.
Message-ID: <1991Apr22.035236.25021@agate.berkeley.edu>
Date: 22 Apr 91 03:52:36 GMT
References: <1991Apr21.041312.1@watt.ccs.tuns.ca> <22498@yunexus.YorkU.CA>
Sender: root@agate.berkeley.edu (Charlie Root)
Organization: University of California, Berkeley
Lines: 21

In article <22498@yunexus.YorkU.CA> rreiner@yunexus.YorkU.CA (Richard Reiner) writes:
>>My guess is that sprite and collision detection cannot be efficiently emulated
>>through software, which is the only way possible with an IBM PC.
>On the other hand, the C64 can do 36 dhrystones/sec (according to the
>machine rankings included with the dhrystone benchmark source), while
>a cached 386-33 does a best-case 13500 dhrystones/sec (according to my
>own measurements: dhrystone 2.0 compiled with MS C 5.1, generating
>286-specific instructions, using the register option).  Thus a 386-33
>is 375 times as fast as a C64.                                 ^^^^^^
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

I know this is a bit off the track but that statement is simply wrong.
Comparing a 386-33 to a C64 using dhrystones is ridiculous, considering
the difference between the processor capabilities.  Besides, in my
experience a C64 managed only 6 dhrystones/sec :-)

-- 
+==========================================================================+
| Noam Mendelson   ..!ucbvax!web!c60b-1eq       | "I haven't lost my mind, |
| c60b-1eq@web.Berkeley.EDU                     |  it's backed up on tape  |
| University of California at Berkeley          |  somewhere."             |