From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org, openexr-devel@nongnu.org, 22049@debbugs.gnu.org
Subject: Re: Test failure of ilmbase-2.2.0 on i686-linux (testBoxAlgo.cpp)
Date: Tue, 08 Dec 2015 15:36:09 -0500 [thread overview]
Message-ID: <87si3cy8xy.fsf@netris.org> (raw)
In-Reply-To: <20151208053857.GA29923@jasmine> (Leo Famulari's message of "Tue, 8 Dec 2015 00:38:57 -0500")
[added 22049@debbugs.gnu.org to the CC list]
Leo Famulari <leo@famulari.name> writes:
> Greetings from Guix! [0]
>
> We're having trouble building ilmbase-2.2.0 for the i686 architecture on
> Linux, with gcc-4.9.3.
>
> The build process fails during testing. Specifically, it fails
> testBoxAlgo, like this:
>
> ImathTest: testBoxAlgo.cpp:892: void {anonymous}::boxMatrixTransform(): Assertion `b21 == b2' failed.
> /gnu/store/isxqjfaglyfsbcv75y8qbqbph8v28ykr-bash-4.3.39/bin/bash: line 5: 4565 Aborted ${dir}$tst
>
> On our mailing list, this was suggested as the nature of the problem
> [1]:
> On Mon, Nov 30, 2015 at 10:14:49PM +0200, Ludovic Courtès wrote:
>> Right. This sounds very much like a rounding issue, whereby the
>> epsilon in floating-point number comparisons is to strict for 32-bit
>> machines.
Given that ilmbase builds successfully in Guix on x86_64, mips64el, and
armhf, and only fails on i686, I believe that Ludovic's suggestion is
right on the mark.
The issue is that the x87 instruction set (used on 32-bit Intel systems
without SSE) uses 80-bit double-extended precision internally. When
these 80-bit results are later converted to 64-bit doubles, they are
rounded a second time. This "double rounding" results in larger
round-off errors than would occur when rounding only once to 64-bit
doubles, as is done when using x86_64, SSE2, or other architectures.
For more on this, see:
https://en.wikipedia.org/wiki/Rounding#Double_rounding
Quoting from that page:
Some computer languages and the IEEE 754-2008 standard dictate that in
straightforward calculations the result should not be rounded twice.
This has been a particular problem with Java as it is designed to be
run identically on different machines, special programming tricks have
had to be used to achieve this with x87 floating point.[1][2]
[1] Samuel A. Figueroa (July 1995). "When is double rounding
innocuous?". ACM SIGNUM Newsletter (ACM) 30 (3):
21–25. doi:10.1145/221332.221334.
[2] Roger Golliver (October 1998). "Efficiently producing default
orthogonal IEEE double results using extended IEEE
hardware". Intel.
<http://www.open-std.org/JTC1/SC22/JSG/docs/m3/docs/jsgn326.pdf>
Hope this helps,
Mark
prev parent reply other threads:[~2015-12-08 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 5:38 Test failure of ilmbase-2.2.0 on i686-linux (testBoxAlgo.cpp) Leo Famulari
2015-12-08 17:06 ` Ludovic Courtès
2015-12-09 3:11 ` Leo Famulari
2015-12-08 20:36 ` Mark H Weaver [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87si3cy8xy.fsf@netris.org \
--to=mhw@netris.org \
--cc=22049@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=openexr-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).