Re: [hatari-devel] Beams TT demo FPU warnings

[ Thread Index | Date Index | More Archives ]


On 02/11/2017 01:14 AM, Eero Tamminen wrote:
On 02/09/2017 12:44 AM, Eero Tamminen wrote:
On 02/08/2017 12:36 AM, Eero Tamminen wrote:
I.e. gwem's 4getful TT-version that regressed, is again
working, and Beams' TT version that has never worked,
works now for the first time with Hatari.

Beams shows at startup many of these broken
looking warnings:
     "Undocumented FPU constant access (index 00"

Could somebody fix that?

The error message format is now fixed, but the error itself
isn't.  When Beams starts, there are 6400 lines of
this warning:
Undocumented FPU constant access (index 5c02)

-> Shown index isn't properly masked with 0x7f in
   the error message (only in the switch case itself).

M68000PRM says following:
The on-chip ROM contains other constants useful only to the on-
chip microcode routines. The values contained at offsets other
than those defined above are reserved for the use of Motorola
and may be different on various mask sets of the floating-point
coprocessor. These undefined values yield the value 0.0 in the

It would be good to have a test program reporting all the possible
FPU constant values. People owning TT machines could then run it
and report the values they get from their 68882 FPUs, so that we
can see whether the mask sets actually differed in reality.  Or
just add one of those sets to Hatari.

	- Eero

Mail converted by MHonArc 2.6.19+