View Issue Details

IDProjectCategoryView StatusLast Update
0005446Rocky-Linux-9lapackpublic2024-01-19 10:22
ReporterGunnar Schmitz Assigned To 
Status newResolutionopen 
Summary0005446: No automatic linking to 32 bit integer version
DescriptionWe noticed that after upgrading from 9.2 to 9.3 one can not automatically link to the 32 bit integer version of lapack. It will always be linked to the 64 bit version, which results in segmentation faults or "illegal parameter" warnings in lapack.

The relevant software versions are:

lapack.x86_64 3.9.0-10.el9
lapack-devel.x86_64 3.9.0-10.el9
lapack-static.x86_64 3.9.0-10.el9
lapack64.x86_64 3.9.0-10.el9
lapack64_.x86_64 3.9.0-10.el9

I attach a simple Fortan program illustrating the issue. As backtrace I get

Backtrace for this error:
#0 0x7fb45f423860 in ???
#1 0x7fb45f422a05 in ???
#2 0x7fb45f054daf in ???
#3 0x7fb45f0ba18a in ???
#4 0x7fb460036664 in ???
#5 0x4016fc in ???
#6 0x401740 in ???
#7 0x7fb45f03feaf in ???
#8 0x7fb45f03ff5f in ???
#9 0x401114 in ???
#10 0xffffffffffffffff in ???
Segmentation fault (core dumped)
Steps To ReproduceI attached a simple Fortran program compiling it with

gfortran -fallow-argument-mismatch main.f90 -L /usr/lib64/ -lblas -L/usr/lib64 -llapack

will always result in a segmentation fault. As a workaround one can compile it with

gfortran -fallow-argument-mismatch -finteger-4-integer-8 main.f90 -L /usr/lib64/ -lblas -L/usr/lib64 -llapack

and it works since all 32-bit integers are replaced with 64-bit integers. In the forum post other workarounds are shown, but I still think it is a bug. At least the behavior is unexpected.
TagsNo tags attached.
Attached Files
lapack_bug.tar.gz (400 bytes)


Issue History

Date Modified Username Field Change
2024-01-19 10:22 Gunnar Schmitz New Issue
2024-01-19 10:22 Gunnar Schmitz File Added: lapack_bug.tar.gz