[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #43891] Difference in results of test chop and

From: Rik
Subject: [Octave-bug-tracker] [bug #43891] Difference in results of test chop and __run_test_suite__
Date: Tue, 06 Jan 2015 02:44:08 +0000
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0

Update of bug #43891 (project octave):

                  Status:                    None => Confirmed              


Follow-up Comment #4:

I can confirm this.  I haven't built the MXE code in about a year so that took
a few hours to get going again.

For your questions, if you don't set any other options the build scripts will
realize that you are targeting a Windows machine and pass the
--enable-float-truncate option.  You can also look in the tmp-octave directory
while it is being built.  The file config.h will have a definition for
FLOAT_TRUNCATE which is the word volatile.

I don't have very good theories about why it would fail when run directly, but
not when run through __run_test_suite__.  I suspect it is something to do with
register pressure and the CPU being forced to take results out of the special
math co-processor registers with 80-bit precision into regular 64-bit
registers (IEEE standard).  


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]