Re: [hatari-devel] FPU tester update request |

[ Thread Index | Date Index | More lists.tuxfamily.org/hatari-devel Archives ]

*To*: hatari-devel@xxxxxxxxxxxxxxxxxxx*Subject*: Re: [hatari-devel] FPU tester update request*From*: Nicolas Pomarède <npomarede@xxxxxxxxxxxx>*Date*: Thu, 9 Aug 2018 13:02:03 +0200

Le 31/07/2018 à 14:58, Toni Wilen a écrit :

It has been more than 1 year now..Here is an updated version of the FPU tester (diagnostic version). I'll release an update to the original testing tool once this has settled.Hi I found some more undocumented FPU behaviors (already implemented by Andreas in softfloat emulation) that are not found by FPU tester:

Hi

Nicolas

--- 68040 FCMP: returns also N-bit set if either parameter is NaN with sign bit set. 6888x and 68060 never return N + NAN flags set simultaneously. Currently FCMP test returns error if CPU is 68040 which is fine for me, at least this confirms FCMP difference. -- Monadic instruction, infinity as input value with high mantissa bit set and instruction also returning infinity (because input was infinity): Valid infinity bit patterns are: 7FFF 00000000 00000000 or 7FFF 80000000 00000000 (+inf) FFFF 00000000 00000000 or FFFF 80000000 00000000 (-inf) 6888x and 68040: returned infinity value is same as input value, mantissa high bit is not cleared. 68060: returned infinity mantissa is always zero. FPU internally generated infinity has always zero mantissa. -- 6888x and 68040 dyadic instruction that returns infinity when either (or both) input values are infinity: Fxxx a, b: if a is infinity: returned infinity equals a (including mantissa high bit). if only b is infinity: returned infinity mantissa high bit is always cleared. 68040 only "inverted" special case: FADD a,b and FSUB a,b: if a is infinity but b isn't: zero mantissa returned. if b is infinity: b is returned as is (with possibility for mantissa high bit being set) -- Above infinity weird cases are not detected by tester. Not that no program most likely cares but it would be interesting to know if these are model specific differences or if it was changed in some later revision.

**Messages sorted by:**[ date | thread ]- Prev by Date:
**[hatari-devel] small bug in DebugCpu_MemDump** - Next by Date:
**[hatari-devel] Changes to improve integration between Hatari and WinUAE cpu core** - Previous by thread:
**Re: [hatari-devel] FPU tester update request** - Next by thread:
**[hatari-devel] small bug in DebugCpu_MemDump**

Mail converted by MHonArc 2.6.19+ | http://listengine.tuxfamily.org/ |