[Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices

[anonymous]

Follow-up Comment #17, bug #58926 (project octave):

@Dmitri: It's to protect our own users who might encounter bugs with MKL and
think that Octave is at fault when Octave really isn't. If you see the links
earlier in the thread, there's a constant theme of language like "BLAS is
innocent, Octave is suspect" etc before realizing that most of these programs
are perfectly fine by themselves but can't work together in some situations.
We also have a section already in the manual (Appendix D) for exactly this
sort of user experience:


This section describes known problems that affect users of Octave. Most of
these are not Octave bugs per se—if they were, we would fix them. But the
result for a user may be like the result of a bug. 


It looks like a good place to list known problems with existing libraries
outside Octave's control and how to work around them. The clash between IOMP
and GOMP is one such.

    _______________________________________________________

Reply to this item at:

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

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