Bug 2142316

Summary: lapack-3.11.0 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: lapackAssignee: Tom "spot" Callaway <spotrh>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dasergatskov, frantisek.kluknavsky, spotrh
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-06-05 14:58:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
bug test fortran program none

Description Upstream Release Monitoring 2022-11-13 01:26:00 UTC
Releases retrieved: 3.11.0
Upstream release that is considered latest: 3.11.0
Current version/release in rawhide: 3.10.1-2.fc37
URL: http://www.netlib.org/lapack/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/1534/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/lapack

Comment 1 Upstream Release Monitoring 2022-11-13 01:26:05 UTC
Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-36na1m_9/lapack.spec']' returned non-zero exit status 1.

StdOut:
error: Bad source: ./v3.11.0.tar.gz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.10/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
  File "/usr/local/lib/python3.10/site-packages/hotness/builders/koji.py", line 188, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Comment 2 Dmitri A. Sergatskov 2022-11-20 16:09:54 UTC
Lapack-3.11 apears to have regression in NaN/Inf handling. See e.g.: 

https://savannah.gnu.org/bugs/?63384

Comment 3 Dmitri A. Sergatskov 2022-11-21 19:31:51 UTC
Filed the issue upstream:

https://github.com/Reference-LAPACK/lapack/issues/763

Dmitri.

Comment 4 Tom "spot" Callaway 2023-06-05 14:58:31 UTC
3.11.0 (plus the fix for 763) is in rawhide.

Comment 5 Dmitri A. Sergatskov 2023-06-05 16:32:50 UTC
Created attachment 1969084 [details]
bug test  fortran program

Comment 6 Dmitri A. Sergatskov 2023-06-05 16:45:20 UTC
May be not directly related to this bug -- trying to recompile src.rpm on Centos Strema 9 with gcc-12 I got the error:

    [100%] Linking C executable VerifyFortranC
    /usr/bin/cmake -E cmake_link_script CMakeFiles/VerifyFortranC.dir/link.txt --verbose=1
    /opt/rh/gcc-toolset-12/root/usr/bin/gcc -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1  -m64 -march=x86-64-v2 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -frecursive --no-optimize-sibling-calls -DNDEBUG -Wl,-z,relro -Wl,--as-needed  -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 CMakeFiles/VerifyFortranC.dir/main.c.o CMakeFiles/VerifyFortranC.dir/VerifyC.c.o -o VerifyFortranC   -L/usr/lib/gcc/x86_64-redhat-linux/11  libVerifyFortran.a -lgfortran -lm -lquadmath -lm 
    /opt/rh/gcc-toolset-12/root/usr/libexec/gcc/x86_64-redhat-linux/12/ld: /tmp/cc8cLNcL.ltrans0.ltrans.o: in function `main':
    /usr/share/cmake/Modules/FortranCInterface/Verify/main.c:14: undefined reference to `VerifyFortran'
    collect2: error: ld returned 1 exit status
    gmake[3]: *** [CMakeFiles/VerifyFortranC.dir/build.make:115: VerifyFortranC] Error 1

With gcc-11 (default) it rebuilds fine.

Dmitri.
--

Comment 7 Dmitri A. Sergatskov 2023-06-05 16:49:05 UTC
I just noticed when I attached the program it wiped my comments. 

With lapack-3.11.0-4.fc39 I see:

$ gfortran bug-63384.f -llapack -lblas
$ ./a.out 
 x = 
                       NaN                       NaN
                       NaN                       NaN
 anorm =                        NaN
 dgetrf info:            0
 ipiv = 
           1           2
 ** On entry to DGECON parameter number  5 had an illegal value
Note: The following floating-point exceptions are signalling: IEEE_INVALID_FLAG
I am not sure if this is a desired behavior. 

With OpenBlas (and with  lapack-3.10) I see:

$ LD_PRELOAD=/usr/lib64/libopenblas.so.0 ./a.out 
 x = 
                       NaN                       NaN
                       NaN                       NaN
 anorm =                        NaN
 dgetrf info:            0
 ipiv = 
           1           2
 dgecon info:            0
 rcond =                        NaN
 dgetri info:            0
 xinv = 
                       NaN                       NaN
                       NaN                       NaN

Dmitri.
--