[Octave-bug-tracker] [bug #48418] MXE Octave: __run_test_suite__ has wrong results

[Mike Miller]

Follow-up Comment #8, bug #48418 (project octave):

Rik: that saving and restoring of the FPUCW is currently in effect. The value
that Avinoam sees after running Java is the correct one, 0x37f, which tells
the processor to use 80-bit extended precision floating point for intermediate
values. The initial value, when the tests fail, 0x27f tells the processor to
truncate all intermediate results to 64-bit double precision values.

So the code to restore the correct value of the FPUCW is working, because it
gets the right value after a Java call. But the initial value is wrong, and I
wonder if it's wrong all the time (which is why I want to see the results in a
non-Java 32-bit build), or wrong because the JVM is linked into Octave and it
is changing the default when Octave starts up, even if it hasn't been called
yet.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?48418>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/