|Re: [hatari-devel] FPU status register handling & fmovem.x bugs|
[ Thread Index | Date Index | More lists.tuxfamily.org/hatari-devel Archives ]
Am 01.06.2018 um 09:40 schrieb Thorsten Otto <admin@xxxxxxxxxxx>:
I have no experience with win32. But as far as I know long double in some environments equals double an is 64-bit wide. I think Visual Studio is affected from this.
Wikipedia: "On the x86 architecture, most C compilers implement long double as the 80-bit extended precision type supported by x86 hardware (sometimes stored as 12 or 16 bytes to maintain data structure alignment), as specified in the C99 / C11 standards (IEC 60559 floating-point arithmetic (Annex F)). An exception is Microsoft Visual C++ for x86, which makes long double a synonym for double."
This was a misunderstanding. I meant the expected value matches documentation (in contrast to FPSR, where it doesn't; see below). Of course the value from the emulated FPU seems be wrong.
In my documentation (MC68881/MC68882 Floating-Point Coprocessor User's Manual, First Edition) I have this:
|Mail converted by MHonArc 2.6.19+||http://listengine.tuxfamily.org/|