Re: [issue18062] m68k FPU precision issue
- To: Thorsten Glaser <tg@mirbsd.de>
- Cc: Python tracker <report@bugs.python.org>, debian-68k@lists.debian.org
- Subject: Re: [issue18062] m68k FPU precision issue
- From: Andreas Schwab <schwab@linux-m68k.org>
- Date: Sun, 26 May 2013 14:27:19 +0200
- Message-id: <[🔎] 87hahqgc48.fsf@hase.home>
- In-reply-to: <Pine.BSM.4.64L.1305252216460.5262__34036.2077848569$1369520399$gmane$org@herc.mirbsd.org> (Thorsten Glaser's message of "Sat, 25 May 2013 22:19:09 +0000 (UTC)")
- References: <1369516829.93.0.967399013079.issue18062@psf.upfronthosting.co.za> <Pine.BSM.4.64L.1305252216460.5262__34036.2077848569$1369520399$gmane$org@herc.mirbsd.org>
Thorsten Glaser <tg@mirbsd.de> writes:
> root@ara3:~ # ./a.out
> test#1 fail: 1.00000000000000000E+00
> test#2 fail: 1.00000000000000040E+16
> changing FPU control word from 00000000 to 00000080 => 00000080
> test#1 fail: 1.00000000000000000E+00
> test#2 fail: 1.00000000000000040E+16
What is the exact sequence of fpu insns?
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Reply to: