<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re:Floating point violation in PARDISO when compiling code with -fpe0 flag (OneAPI 2025.3) in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Floating-point-violation-in-PARDISO-when-compiling-code-with/m-p/1747778#M37586</link>
    <description>&lt;P&gt;The bug has been fixed and the fix is included in 2026.0 release.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Regards, &lt;/P&gt;&lt;P&gt;Alex&lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 13 May 2026 09:45:25 GMT</pubDate>
    <dc:creator>Aleksandra_K</dc:creator>
    <dc:date>2026-05-13T09:45:25Z</dc:date>
    <item>
      <title>Floating point violation in PARDISO when compiling code with -fpe0 flag (OneAPI 2025.3)</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Floating-point-violation-in-PARDISO-when-compiling-code-with/m-p/1733096#M37493</link>
      <description>&lt;P&gt;Hi, we've noted when switching to 2025.3 that some of our verification cases are crashing with an FP violation when calling the paradiso solver PHASE=33. It is related to ifx and using the -fpe0 flag. Here I prepared a standalone code that shows the issue. The RHS for this case is 0. The matrix comes from a 4x10 discretization of the Poisson equation with Neumann and Periodic BCs. Using Dirichlet led to the same outcome.&lt;/P&gt;&lt;P&gt;Copy both files in a directory and type in the commend window (linux):&lt;/P&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;$ ifx -O0 -fpe0 -fpp test_pardiso.f90 -qmkl -o test_pardiso&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;$ ./test_pardiso Matrix_H_ULMAT.txt -2 1&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is what I'm seeing:&lt;/P&gt;&lt;PRE&gt;(fds_python_env) mnv@spark-login PARDISO_TEST $ ./test_pardiso Matrix_H_ULMAT.txt -2 1&lt;BR /&gt;--- test_pardiso ---&lt;BR /&gt;Matrix file: Matrix_H_ULMAT.txt&lt;BR /&gt;N: 40&lt;BR /&gt;NNZ (upper triangle incl diag): 106&lt;BR /&gt;MTYPE: -2&lt;BR /&gt;MSGLVL: 1&lt;BR /&gt;&lt;BR /&gt;=== PARDISO: solving a symmetric indefinite system ===&lt;BR /&gt;Matrix checker is turned ON&lt;BR /&gt;1-based array indexing is turned ON&lt;BR /&gt;PARDISO double precision computation is turned ON&lt;BR /&gt;METIS algorithm at reorder step is turned ON&lt;BR /&gt;Scaling is turned ON&lt;BR /&gt;Matching is turned ON&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Summary: ( reordering phase )&lt;BR /&gt;================&lt;BR /&gt;&lt;BR /&gt;Times:&lt;BR /&gt;======&lt;BR /&gt;Time spent in calculations of symmetric matrix portrait (fulladj): 0.000013 s&lt;BR /&gt;Time spent in reordering of the initial matrix (reorder) : 0.000000 s&lt;BR /&gt;Time spent in symbolic factorization (symbfct) : 0.000308 s&lt;BR /&gt;Time spent in data preparations for factorization (parlist) : 0.000010 s&lt;BR /&gt;Time spent in allocation of internal data structures (malloc) : 0.000121 s&lt;BR /&gt;Time spent in matching/scaling : 0.000463 s&lt;BR /&gt;Time spent in additional calculations : 0.002366 s&lt;BR /&gt;Total time spent : 0.003281 s&lt;BR /&gt;&lt;BR /&gt;Statistics:&lt;BR /&gt;===========&lt;BR /&gt;Parallel Direct Factorization is running on 4 OpenMP&lt;BR /&gt;&lt;BR /&gt;&amp;lt; Linear system Ax = b &amp;gt;&lt;BR /&gt;number of equations: 40&lt;BR /&gt;number of non-zeros in A: 106&lt;BR /&gt;number of non-zeros in A (%): 6.625000&lt;BR /&gt;&lt;BR /&gt;number of right-hand sides: 1&lt;BR /&gt;&lt;BR /&gt;&amp;lt; Factors L and U &amp;gt;&lt;BR /&gt;number of columns for each panel: 128&lt;BR /&gt;number of independent subgraphs: 0&lt;BR /&gt;&amp;lt; Preprocessing with state of the art partitioning metis&amp;gt;&lt;BR /&gt;number of supernodes: 29&lt;BR /&gt;size of largest supernode: 8&lt;BR /&gt;number of non-zeros in L: 244&lt;BR /&gt;number of non-zeros in U: 1&lt;BR /&gt;number of non-zeros in L+U: 245&lt;BR /&gt;=== PARDISO is running in In-Core mode, because iparam(60)=0 ===&lt;BR /&gt;&lt;BR /&gt;Percentage of computed non-zeros for LL^T factorization&lt;BR /&gt;1 % 3 % 4 % 5 % 7 % 9 % 11 % 12 % 15 % 17 % 19 % 22 % 25 % 43 % 45 % 47 % 49 % 50 % 51 % 54 % 56 % 58 % 60 % 62 % 65 % 67 % 71 % 73 % 100 %&lt;BR /&gt;&lt;BR /&gt;=== PARDISO: solving a symmetric indefinite system ===&lt;BR /&gt;Single-level factorization algorithm is turned ON&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Summary: ( factorization phase )&lt;BR /&gt;================&lt;BR /&gt;&lt;BR /&gt;Times:&lt;BR /&gt;======&lt;BR /&gt;Time spent in copying matrix to internal data structure (A to LU): 0.000000 s&lt;BR /&gt;Time spent in factorization step (numfct) : 0.000259 s&lt;BR /&gt;Time spent in allocation of internal data structures (malloc) : 0.000017 s&lt;BR /&gt;Time spent in additional calculations : 0.000000 s&lt;BR /&gt;Total time spent : 0.000276 s&lt;BR /&gt;&lt;BR /&gt;Statistics:&lt;BR /&gt;===========&lt;BR /&gt;Parallel Direct Factorization is running on 4 OpenMP&lt;BR /&gt;&lt;BR /&gt;&amp;lt; Linear system Ax = b &amp;gt;&lt;BR /&gt;number of equations: 40&lt;BR /&gt;number of non-zeros in A: 106&lt;BR /&gt;number of non-zeros in A (%): 6.625000&lt;BR /&gt;&lt;BR /&gt;number of right-hand sides: 1&lt;BR /&gt;&lt;BR /&gt;&amp;lt; Factors L and U &amp;gt;&lt;BR /&gt;number of columns for each panel: 128&lt;BR /&gt;number of independent subgraphs: 0&lt;BR /&gt;&amp;lt; Preprocessing with state of the art partitioning metis&amp;gt;&lt;BR /&gt;number of supernodes: 29&lt;BR /&gt;size of largest supernode: 8&lt;BR /&gt;number of non-zeros in L: 244&lt;BR /&gt;number of non-zeros in U: 1&lt;BR /&gt;number of non-zeros in L+U: 245&lt;BR /&gt;gflop for the numerical factorization: 0.000001&lt;BR /&gt;&lt;BR /&gt;gflop/s for the numerical factorization: 0.005276&lt;BR /&gt;&lt;BR /&gt;forrtl: error (65): floating invalid&lt;BR /&gt;Image PC Routine Line Source &lt;BR /&gt;libc.so.6 0000150BEA63EBF0 Unknown Unknown Unknown&lt;BR /&gt;libmkl_intel_thre 0000150BF0AF3FA4 mkl_pds_lp64_pds_ Unknown Unknown&lt;BR /&gt;libmkl_core.so.2 0000150BECF82D66 mkl_pds_lp64_do_a Unknown Unknown&lt;BR /&gt;libmkl_core.so.2 0000150BECB99A33 mkl_pds_lp64_pard Unknown Unknown&lt;BR /&gt;libmkl_core.so.2 0000150BECF97C1E mkl_pds_lp64_pard Unknown Unknown&lt;BR /&gt;test_pardiso 0000000000406071 Unknown Unknown Unknown&lt;BR /&gt;test_pardiso 00000000004052BD Unknown Unknown Unknown&lt;BR /&gt;libc.so.6 0000150BEA6295D0 Unknown Unknown Unknown&lt;BR /&gt;libc.so.6 0000150BEA629680 __libc_start_main Unknown Unknown&lt;BR /&gt;test_pardiso 00000000004051D5 Unknown Unknown Unknown&lt;/PRE&gt;&lt;P&gt;This is new, we don't see this issue with 2025.2.&lt;/P&gt;</description>
      <pubDate>Sat, 10 Jan 2026 13:51:56 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Floating-point-violation-in-PARDISO-when-compiling-code-with/m-p/1733096#M37493</guid>
      <dc:creator>Marcos_V_1</dc:creator>
      <dc:date>2026-01-10T13:51:56Z</dc:date>
    </item>
    <item>
      <title>Re: Floating point violation in PARDISO when compiling code with -fpe0 flag (OneAPI 2025.3)</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Floating-point-violation-in-PARDISO-when-compiling-code-with/m-p/1733279#M37495</link>
      <description>&lt;P&gt;Thanks for reporting this issue. I can reproduce it on my side. We will take a look at this one and get back to you once there is any update.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks!&lt;/P&gt;
&lt;P&gt;Fengrui&lt;/P&gt;</description>
      <pubDate>Mon, 12 Jan 2026 23:39:02 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Floating-point-violation-in-PARDISO-when-compiling-code-with/m-p/1733279#M37495</guid>
      <dc:creator>Fengrui</dc:creator>
      <dc:date>2026-01-12T23:39:02Z</dc:date>
    </item>
    <item>
      <title>Re:Floating point violation in PARDISO when compiling code with -fpe0 flag (OneAPI 2025.3)</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Floating-point-violation-in-PARDISO-when-compiling-code-with/m-p/1747778#M37586</link>
      <description>&lt;P&gt;The bug has been fixed and the fix is included in 2026.0 release.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Regards, &lt;/P&gt;&lt;P&gt;Alex&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 13 May 2026 09:45:25 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Floating-point-violation-in-PARDISO-when-compiling-code-with/m-p/1747778#M37586</guid>
      <dc:creator>Aleksandra_K</dc:creator>
      <dc:date>2026-05-13T09:45:25Z</dc:date>
    </item>
  </channel>
</rss>

