[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-
From: |
Archisman Panigrahi |
Subject: |
[Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices |
Date: |
Tue, 11 Aug 2020 03:23:37 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:75.0) Gecko/20100101 Firefox/75.0 |
Follow-up Comment #12, bug #58926 (project octave):
[comment #10 comment #10:]
> Regarding comment #6: Thank you for sharing your knowledge.
>
> Regarding comment #8: Thank you for testing the workaround of comment #6.
>
> I agree that Octave should better inform Intel MKL users. Do you have
suggestions were to add this information? If you know a suitable wiki
location, please go ahead and add this information (everybody is an author)
😉
Maybe a new page titled "Using Octave with Intel MKL in Debian based systems"
can be created?
>
> On the other hand, I do not think that this is a severe bug. A workaround
exists and Octave does not recommend or rely on the Intel MKL. Boldly
speaking, it was your decision to use the Intel MKL with Octave (at your own
risk). Same goes for self-compiled libraries, etc. It is impossible to
regard all possible library and parameter combinations.
>
I competely agree with you that it is my responsibility when I use a non-free
external library like MKL, but it should still be well documented as MKL is
quite popular.
> A general recommendation is to run the Octave test suite when changing from
default packages (reference BLAS, OpenBLAS)
>
> +verbatim-
> __run_test_suite__
>
>
> This takes only about 5 minutes and should reveal such bugs.
Although Octave executed my program correctly, it fails in the test_suite even
after using
export MKL_THREADING_LAYER=gnu
Here is the output.
octave:1> __run_test_suite__
Integrated test scripts:
liboctave/array/Array.cc-tst ................................... PASS
21/21
liboctave/array/CMatrix.cc-tst ................................. PASS
9/11
FAIL 2
liboctave/array/CSparse.cc-tst ................................. PASS
10/10
liboctave/array/Sparse.cc-tst .................................. PASS
107/107
liboctave/array/dMatrix.cc-tst ................................. PASS
10/10
liboctave/array/dSparse.cc-tst ................................. PASS
12/12
liboctave/array/fCMatrix.cc-tst ................................fatal:
caught signal Segmentation fault -- stopping myself...
Segmentation fault (core dumped)
Without the export command, the output is
Integrated test scripts:
liboctave/array/Array.cc-tst ................................... PASS
21/21
liboctave/array/CMatrix.cc-tst .................................fatal:
caught signal Segmentation fault -- stopping myself...
Segmentation fault (core dumped)
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?58926>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, (continued)
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, anonymous, 2020/08/10
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, anonymous, 2020/08/10
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, Archisman Panigrahi, 2020/08/10
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, anonymous, 2020/08/10
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, anonymous, 2020/08/10
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, Kai Torben Ohlhus, 2020/08/11
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, Archisman Panigrahi, 2020/08/11
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, Archisman Panigrahi, 2020/08/11
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, Kai Torben Ohlhus, 2020/08/11
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, Kai Torben Ohlhus, 2020/08/11
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices,
Archisman Panigrahi <=
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, anonymous, 2020/08/11
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, Dmitri A. Sergatskov, 2020/08/11
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, Archisman Panigrahi, 2020/08/11
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, Dmitri A. Sergatskov, 2020/08/11
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, anonymous, 2020/08/11
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, anonymous, 2020/08/11
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, anonymous, 2020/08/11
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, anonymous, 2020/08/11
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, John W. Eaton, 2020/08/11
- [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices, John W. Eaton, 2020/08/11