Re: [hatari-devel] WinUAE Falcon emulation and FPU

[ Thread Index | Date Index | More Archives ]

Hi all,

Are there a lot of demos that *require* FPU?

I did a few tests with some FPU required demos.
It seemed to work quite well, except for one : Eskimau

This demo is a 68060 + accelerator board Falcon, but the code is pure 68030+FPU.
To run it, just use the new cpu + 68030 + DSP + 14 Meg + 32 Mhz CPU.

The sound is horrible, but you can listen it a bit under the loud noise.

In this demo, 2 screens seem to show little problems : the tridi world and the tridi hand. On some borders of the tridi objects, there are some lines that are bigger than it should be.

I'm pretty sure it's about rounding or bugs in the FPU emulation, but I don't know it enough to investigate.



PS : it's one of the few 68060 demos that run with hatari (with sound problems)

Le 28/09/2012 22:12, Eero Tamminen a écrit :

On perjantai 28 syyskuu 2012, Thomas Huth wrote:
schrieb Eero Tamminen <oak@xxxxxxxxxxxxxx>:
The reason seems to be that WinUAE core defaults
FPU to "none".  If I select any other FPU option,
the demo works fine.

Does old UAE core 030 setting emulate FPU?
Yes, that's why the GUI says "68EC030+FPU" when you
select this CPU level.
Why old UAE core emulates by default something which
isn't standard on 030?

As Falcon has 68030 which doesn't include FPU and
Falcon didn't include a separate FPU, how this demo
can work on real Falcon?
It doesn't work on a non-FPU Falcon. Just read the
read_me.1st file that is shipped with the demo.
Thanks, I missed that.  I was in hurry to be somewhere
else when I noticed the issue (I had first thought it
was EmuTOS regression because I've naturally tested
earlier EmuTOS versions only with old UAE core).

IMHO it would be better to add something about that
at least to the compatibility list.  These kinds of
differences between our emulation cores can be a bit

	- Eero

Mail converted by MHonArc 2.6.19+