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

[Doron Behar]

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

[comment #109 comment #109:]
> You can build Octave with 64bit indexing inside Octave but still use
BLAS/LAPACK (and related) libraries that use 32bit indexing. 

I was not able to make the configure report put out this:


  64-bit array dims and indexing:       yes
  64-bit BLAS array dims and indexing:  yes


When I used the reference blas and lapack implementations, I got instead:


  64-bit array dims and indexing:       yes
  64-bit BLAS array dims and indexing:  no


Perhaps that's intended, and if not, perhaps it's due to how the reference
blas implementation is built on NixOS:

https://github.com/NixOS/nixpkgs/blob/8a5eb89b0f70999c08ce9ce6df89238671e186dc/pkgs/build-support/alternatives/blas/default.nix

I'm building up a benchmark table where every blas implementation is tested,
against Octave 6.0.90 and 5.2.0, and I'll report the results (probably
tomorrow) in NixOS' discourse thread. The benchmark I'm using is this:
https://openbenchmarking.org/test/system/octave-benchmark .

    _______________________________________________________

Reply to this item at:

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

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