60 FPU disable patch

[SpeedGeek]

Cosmos asked me to post this message:

Hi (SpeedGeek)!

I just checked with WinUAE beta 17 your following code :
[060 FPU disable patch]

Your small code freeze the boot with WinUAE CPU 68020 and 68040...

Works fine only with CPU 68060...

Could you check with Toni Wilen for fixing the bug ?

Thanks,

Here's my reply:

That's the problem with emulation... it's never 100% the same as a real 68K CPU! It works with a real 030, 040 and 060 so WinUAE must have some difference in the exception code handling.

Does WinUAE use the correct stack frame? Does it execute this code in Supervisor mode with proper emulation? Does it generate the correct exception vector for illegal instructions? Does it emulate the VBR correctly?

It's up to Toni Wilen to fix this problem (I'll post your bug report on EAB)...

P.S. I assume you already know the email address for Cosmos.

[Toni Wilen]

Originally Posted by SpeedGeek

Cosmos asked me to post this message:

Sorry but..

First, this surely has nothing to with this beta series.. (see first post)
Also there was no useful information whatsoever in that message and I don't ask details via email and finally, information included has to be correct or nothing would work!

EDIT: Code talks. Not guesses.

[SpeedGeek]

Originally Posted by Toni Wilen

Sorry but..

First, this surely has nothing to with this beta series.. (see first post)
Also there was no useful information whatsoever in that message and I don't ask details via email and finally, information included has to be correct or nothing would work!

EDIT: Code talks. Not guesses.

1) The FPU disable patch code is not in Amiga executable format (it only works when patched into exec.library)

2) Cosmos didn't send me what you may consider a proper WinUAE bug report

3) I don't have a WinUAE system, so if you don't you want to email Cosmos then your only option would be to download one of his exec patches and generate your own WinUAE bug report

4) I write and test my code on real 68K Amiga's so why do you (or Cosmos) think it's my problem if it fails with WinUAE?

[Toni Wilen]

I didn't say anything about code having problem, I only said that if there is code that does not work that should work, then I do nothing unless I have exact same code with exact same config.

There has been countless "bugs" that were actually caused by bad config, bad code that works accidentally with developer's config/real hardware and so on = Proper test case required. I don't waste time by guessing.