[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #49166] "system.tst" fails under Windows
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #49166] "system.tst" fails under Windows |
Date: |
Wed, 28 Sep 2016 05:17:32 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:43.0) Gecko/20100101 Firefox/43.0 |
Follow-up Comment #4, bug #49166 (project octave):
Well, it looks like I know what is happening; But, I don't like the results.
I re-compiled a version of Octave via MXE where I truncated the intermediate
results in Fcputime in data.cc.
I changed
double usr = cpu_tm.user ();
double sys = cpu_tm.system ();
to
OCTAVE_FLOAT_TRUNCATE double usr = cpu_tm.user ();
OCTAVE_FLOAT_TRUNCATE double sys = cpu_tm.system ();
The script which used to fail on the first or second iteration now passes 200
iterations without problem.
I'm adding jwe to the CC list for the bug. This is a fairly large
architectural question. Do we want to find all places in the code where there
is a potential for extra precision to be maintained and use
OCTAVE_FLOAT_TRUNCATE? Or do we want to just add a tolerance to the BIST
tests whenever we encounter these issues? I'm tempted to mark this as
Postponed since I don't think the answer will be clear before the 4.2.0
release is made.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?49166>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/