|
From: | Kai Torben Ohlhus |
Subject: | [Octave-bug-tracker] [bug #58926] Octave gives wrong results with intel-mkl when diagonalizing large matrices |
Date: | Tue, 11 Aug 2020 02:56:42 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.125 Safari/537.36 |
Update of bug #58926 (project octave): Item Group: None => Incorrect Result _______________________________________________________ Follow-up 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) 😉 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. 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. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?58926> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |