[Octave-bug-tracker] [bug #57591] Segmentation faults when running the test suite (mostly with clang)

[Rik]

Follow-up Comment #110, bug #57591 (project octave):

Summarizing the experience of Octave developers to date which Markus relayed:

1) Building Octave with 64-bit pointers is routine and is the default in the
configure script (you have to go out of your way to use 32-bit pointers.

2) Building Fortran libraries with 64-bit pointers is problematic (not always,
but enough of the time to not make it a default).  This isn't code that Octave
controls so if there are issues you will need to go to the authors of the
particular packages.  What has been discovered is that you need absolute
consistency between all of the libraries for this to have even a chance of
working.  If one library is built with 64-bit pointers, they all need to be
built that way.

3) Performance and correctness are in pseudo-opposition.  The tradeoffs a
library coder makes for performance may cause slight deviations from reference
behavior.  The choice of which feature to prioritize is left to the user.  If
they want performance they can install ATLAS or OpenBLAS.  If they are worried
about conformance to standard they can install a reference BLAS.  Octave has
chosen to leave the decision to users.  I think distributions should as well
and make various BLAS libraries available for selection by the user.

4) Intel MKL BLAS is definitely high performance, but definitely has bugs
reported against it on the Octave bug tracker.  I see that you plan not to use
it for other reasons (non-free software), but that will make your life easier
in this case. 

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57591>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/