Ticket #70132: main.log

version:1
:debug:main Starting logging for py27-scipy @1.2.3_1+gfortran+openblas
:debug:sysinfo macOS 14.5 (darwin/23.5.0) arch arm
:debug:sysinfo MacPorts 2.9.3
:debug:sysinfo Xcode none, CLT 15.3.0.0.1.1708646388
:debug:sysinfo SDK 14
:debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 14.0
:debug:main Fetching py27-scipy-1.2.3_1+gfortran+openblas.darwin_23.arm64.tbz2 archive size
:debug:main epoch: in tree: 0 installed: 0
:debug:main py27-numpy 1.16.6_4 exists in the ports tree
:debug:main py27-numpy 1.16.6_4 +gfortran is the latest installed
:debug:main py27-numpy 1.16.6_4 +gfortran is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/python/py-numpy
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Re-registering default for distname
:debug:main Re-registering default for build.cmd
:debug:main Re-registering default for build.target
:debug:main Re-registering default for destroot.cmd
:debug:main Re-registering default for destroot.destdir
:debug:main Re-registering default for destroot.target
:debug:main Re-registering default for test.cmd
:debug:main Re-registering default for test.target
:debug:main Sourcing PortGroup python 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/python-1.0.tcl
:debug:main Sourcing PortGroup github 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/github-1.0.tcl
:debug:main Sourcing PortGroup active_variants 1.1 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/active_variants-1.1.tcl
:debug:main GCC versions for Darwin 23 arm - 10 11 12 13 devel
:debug:main Clang versions for Darwin 23 arm - 11 12 13 14 15 16 17 18 devel
:debug:main Sourcing PortGroup compilers 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compilers-1.0.tcl
:debug:main Sourcing PortGroup compiler_blacklist_versions 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compiler_blacklist_versions-1.0.tcl
:debug:main Re-registering default for master_sites
:debug:main Re-registering default for extract.rename
:debug:main Re-registering default for livecheck.url
:debug:main Re-registering default for livecheck.regex
:debug:main compiler clang 1500.3.9.4 not blacklisted because it doesn't match {clang < 1100}
:debug:main Re-registering default for homepage
:debug:main Re-registering default for master_sites
:debug:main Re-registering default for extract.rename
:debug:main Re-registering default for livecheck.url
:debug:main Re-registering default for livecheck.regex
:debug:main Compiler gcc44 not available for Darwin23 arm
:debug:main Compiler gcc45 not available for Darwin23 arm
:debug:main Compiler gcc46 not available for Darwin23 arm
:debug:main Compiler gcc47 not available for Darwin23 arm
:debug:main Compiler gcc48 not available for Darwin23 arm
:debug:main adding the default universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Executing variant gfortran provides gfortran
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Running callback python_add_dependencies
:debug:main Finished running callback python_add_dependencies
:debug:main Running callback compilers::add_fortran_legacy_support
:debug:main Finished running callback compilers::add_fortran_legacy_support
:debug:main No need to upgrade! py27-numpy 1.16.6_4 >= py27-numpy 1.16.6_4
:debug:main epoch: in tree: 0 installed: 0
:debug:main fftw-3 3.3.10_0 exists in the ports tree
:debug:main fftw-3 3.3.10_0 +gfortran is the latest installed
:debug:main fftw-3 3.3.10_0 +gfortran is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/math/fftw-3
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup muniversal 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl
:debug:main Sourcing PortGroup compiler_blacklist_versions 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compiler_blacklist_versions-1.0.tcl
:debug:main Sourcing PortGroup active_variants 1.1 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/active_variants-1.1.tcl
:debug:main GCC versions for Darwin 23 arm - 10 11 12 13 devel
:debug:main Clang versions for Darwin 23 arm - 11 12 13 14 15 16 17 18 devel
:debug:main Sourcing PortGroup compilers 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compilers-1.0.tcl
:debug:main Sourcing PortGroup mpi 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/mpi-1.0.tcl
:debug:main Sourcing PortGroup xcode_workaround 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/xcode_workaround-1.0.tcl
:debug:main compiler clang 1500.3.9.4 not blacklisted because it doesn't match {clang <= 211.10.1}
:debug:main muniversal: adding universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Executing variant gfortran provides gfortran
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Running callback compilers::add_fortran_legacy_support
:debug:main Finished running callback compilers::add_fortran_legacy_support
:debug:main Running callback xcode_workaround::xcode_workaround.appy_fix
:debug:main Finished running callback xcode_workaround::xcode_workaround.appy_fix
:debug:main No need to upgrade! fftw-3 3.3.10_0 >= fftw-3 3.3.10_0
:debug:main epoch: in tree: 3 installed: 3
:debug:main libgcc 7.0_0 exists in the ports tree
:debug:main libgcc 7.0_0  is the latest installed
:debug:main libgcc 7.0_0  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/lang/libgcc
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup select 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/select-1.0.tcl
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main universal variant already exists, so not adding the default one
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main No need to upgrade! libgcc 7.0_0 >= libgcc 7.0_0
:debug:main epoch: in tree: 0 installed: 0
:debug:main libgcc13 13.2.0_4 exists in the ports tree
:debug:main libgcc13 13.2.0_4 +stdlib_flag is the latest installed
:debug:main libgcc13 13.2.0_4 +stdlib_flag is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/lang/gcc13
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup select 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/select-1.0.tcl
:debug:main Sourcing PortGroup compiler_blacklist_versions 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compiler_blacklist_versions-1.0.tcl
:debug:main Sourcing PortGroup active_variants 1.1 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/active_variants-1.1.tcl
:debug:main Sourcing PortGroup conflicts_build 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/conflicts_build-1.0.tcl
:debug:main compiler clang 1500.3.9.4 not blacklisted because it doesn't match {clang < 800}
:debug:main compiler llvm-gcc-4.2 blacklisted because it's not installed or it doesn't work
:debug:main compiler clang 1500.3.9.4 not blacklisted because it doesn't match {clang < 1001}
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main universal variant already exists, so not adding the default one
:debug:main Executing variant stdlib_flag provides stdlib_flag
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main No need to upgrade! libgcc13 13.2.0_4 >= libgcc13 13.2.0_4
:debug:main epoch: in tree: 0 installed: 0
:debug:main zlib 1.3.1_0 exists in the ports tree
:debug:main zlib 1.3.1_0  is the latest installed
:debug:main zlib 1.3.1_0  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/archivers/zlib
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup xcodeversion 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/xcodeversion-1.0.tcl
:debug:main adding the default universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main No need to upgrade! zlib 1.3.1_0 >= zlib 1.3.1_0
:debug:main epoch: in tree: 0 installed: 0
:debug:main libiconv 1.17_0 exists in the ports tree
:debug:main libiconv 1.17_0  is the latest installed
:debug:main libiconv 1.17_0  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/textproc/libiconv
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Re-registering default for configure.universal_args
:debug:main Re-registering default for configure.cc_archflags
:debug:main Re-registering default for configure.objc_archflags
:debug:main Re-registering default for configure.cxx_archflags
:debug:main Re-registering default for configure.objcxx_archflags
:debug:main Re-registering default for configure.fc_archflags
:debug:main Re-registering default for configure.f90_archflags
:debug:main Re-registering default for configure.f77_archflags
:debug:main Re-registering default for configure.ld_archflags
:debug:main Re-registering default for configure.universal_cflags
:debug:main Re-registering default for configure.universal_objcflags
:debug:main Re-registering default for configure.universal_cxxflags
:debug:main Re-registering default for configure.universal_objcxxflags
:debug:main Re-registering default for configure.universal_cppflags
:debug:main Re-registering default for configure.universal_ldflags
:debug:main Sourcing PortGroup muniversal 1.1 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/muniversal-1.1.tcl
:debug:main Sourcing PortGroup clang_dependency 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/clang_dependency-1.0.tcl
:debug:main muniversal: adding universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Running callback muniversal::add_compiler_flags
:debug:main Finished running callback muniversal::add_compiler_flags
:debug:main No need to upgrade! libiconv 1.17_0 >= libiconv 1.17_0
:debug:main epoch: in tree: 0 installed: 0
:debug:main py27-cython 3.0.10_0 exists in the ports tree
:debug:main py27-cython 3.0.10_0  is the latest installed
:debug:main py27-cython 3.0.10_0  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/python/py-cython
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Re-registering default for distname
:debug:main Re-registering default for build.cmd
:debug:main Re-registering default for build.target
:debug:main Re-registering default for destroot.cmd
:debug:main Re-registering default for destroot.destdir
:debug:main Re-registering default for destroot.target
:debug:main Re-registering default for test.cmd
:debug:main Re-registering default for test.target
:debug:main Sourcing PortGroup python 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/python-1.0.tcl
:debug:main Sourcing PortGroup select 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/select-1.0.tcl
:debug:main Sourcing PortGroup compiler_blacklist_versions 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compiler_blacklist_versions-1.0.tcl
:debug:main compiler clang 1500.3.9.4 not blacklisted because it doesn't match {clang < 421}
:debug:main adding the default universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Running callback python_add_dependencies
:debug:main Finished running callback python_add_dependencies
:debug:main No need to upgrade! py27-cython 3.0.10_0 >= py27-cython 3.0.10_0
:debug:main epoch: in tree: 0 installed: 0
:debug:main py27-setuptools 44.1.1_0 exists in the ports tree
:debug:main py27-setuptools 44.1.1_0  is the latest installed
:debug:main py27-setuptools 44.1.1_0  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/python/py-setuptools
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Re-registering default for distname
:debug:main Re-registering default for build.cmd
:debug:main Re-registering default for build.target
:debug:main Re-registering default for destroot.cmd
:debug:main Re-registering default for destroot.destdir
:debug:main Re-registering default for destroot.target
:debug:main Re-registering default for test.cmd
:debug:main Re-registering default for test.target
:debug:main Sourcing PortGroup python 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/python-1.0.tcl
:debug:main only one arch supported, so not adding the default universal variant
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Running callback python_add_dependencies
:debug:main Finished running callback python_add_dependencies
:debug:main No need to upgrade! py27-setuptools 44.1.1_0 >= py27-setuptools 44.1.1_0
:debug:main epoch: in tree: 2 installed: 2
:debug:main python27 2.7.18_10 exists in the ports tree
:debug:main python27 2.7.18_10 +lto+optimizations is the latest installed
:debug:main python27 2.7.18_10 +lto+optimizations is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/lang/python27
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup select 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/select-1.0.tcl
:debug:main Sourcing PortGroup clang_dependency 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/clang_dependency-1.0.tcl
:debug:main Sourcing PortGroup compiler_wrapper 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compiler_wrapper-1.0.tcl
:debug:main Sourcing PortGroup openssl 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/openssl-1.0.tcl
:debug:main openssl: branch_proc set : Branch 1.1
:debug:main openssl: Set OpenSSL Branch dependency 1.1
:debug:main openssl: Configure Types 'env_vars pkgconfig build_flags' Branch 1.1
:debug:main openssl: -> Setting openssl environment variable configuration
:debug:main openssl:  -> Will append OPENSSLDIR=/opt/local/libexec/openssl11 to extract.env
:debug:main openssl:  -> Will append OPENSSLDIR=/opt/local/libexec/openssl11 to configure.env
:debug:main openssl:  -> Will append OPENSSLDIR=/opt/local/libexec/openssl11 to build.env
:debug:main openssl:  -> Will append OPENSSLDIR=/opt/local/libexec/openssl11 to destroot.env
:debug:main openssl:  -> Will append OPENSSLDIR=/opt/local/libexec/openssl11 to test.env
:debug:main openssl:  -> Will append OPENSSL_DIR=/opt/local/libexec/openssl11 to extract.env
:debug:main openssl:  -> Will append OPENSSL_DIR=/opt/local/libexec/openssl11 to configure.env
:debug:main openssl:  -> Will append OPENSSL_DIR=/opt/local/libexec/openssl11 to build.env
:debug:main openssl:  -> Will append OPENSSL_DIR=/opt/local/libexec/openssl11 to destroot.env
:debug:main openssl:  -> Will append OPENSSL_DIR=/opt/local/libexec/openssl11 to test.env
:debug:main openssl: -> Setting openssl pkgconfig configuration
:debug:main openssl: -> Setting openssl build flags configuration
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main universal variant already exists, so not adding the default one
:debug:main Executing variant optimizations provides optimizations
:debug:main Executing variant lto provides lto
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Running callback compwrap::configure_envs
:debug:main Finished running callback compwrap::configure_envs
:debug:main Running callback openssl::set_openssl_dependency
:debug:main openssl: Set OpenSSL Branch dependency 1.1
:debug:main Finished running callback openssl::set_openssl_dependency
:debug:main Running callback openssl::check_for_cmake
:debug:main Finished running callback openssl::check_for_cmake
:debug:main Running callback openssl::configure_build
:debug:main Finished running callback openssl::configure_build
:debug:main No need to upgrade! python27 2.7.18_10 >= python27 2.7.18_10
:debug:main epoch: in tree: 0 installed: 0
:debug:main bzip2 1.0.8_0 exists in the ports tree
:debug:main bzip2 1.0.8_0  is the latest installed
:debug:main bzip2 1.0.8_0  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/archivers/bzip2
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main universal variant already exists, so not adding the default one
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main No need to upgrade! bzip2 1.0.8_0 >= bzip2 1.0.8_0
:debug:main epoch: in tree: 0 installed: 0
:debug:main db48 4.8.30_5 exists in the ports tree
:debug:main db48 4.8.30_5  is the latest installed
:debug:main db48 4.8.30_5  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/databases/db48
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup muniversal 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl
:debug:main Sourcing PortGroup clang_dependency 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/clang_dependency-1.0.tcl
:debug:main muniversal: adding universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main No need to upgrade! db48 4.8.30_5 >= db48 4.8.30_5
:debug:main epoch: in tree: 0 installed: 0
:debug:main expat 2.6.2_0 exists in the ports tree
:debug:main expat 2.6.2_0  is the latest installed
:debug:main expat 2.6.2_0  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/textproc/expat
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup muniversal 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl
:debug:main muniversal: adding universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main No need to upgrade! expat 2.6.2_0 >= expat 2.6.2_0
:debug:main epoch: in tree: 0 installed: 0
:debug:main gettext-runtime 0.22.5_0 exists in the ports tree
:debug:main gettext-runtime 0.22.5_0  is the latest installed
:debug:main gettext-runtime 0.22.5_0  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/gettext
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup clang_dependency 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/clang_dependency-1.0.tcl
:debug:main Sourcing PortGroup compiler_blacklist_versions 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compiler_blacklist_versions-1.0.tcl
:debug:main Sourcing PortGroup gnulib 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/gnulib-1.0.tcl
:debug:main Sourcing PortGroup muniversal 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl
:debug:main compiler clang 1500.3.9.4 not blacklisted because it doesn't match {clang < 211.10.1}
:debug:main muniversal: adding universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Running callback gnulib::setup
:debug:main Finished running callback gnulib::setup
:debug:main No need to upgrade! gettext-runtime 0.22.5_0 >= gettext-runtime 0.22.5_0
:debug:main epoch: in tree: 20090923 installed: 20090923
:debug:main libedit 20230828-3.1_0 exists in the ports tree
:debug:main libedit 20230828-3.1_0  is the latest installed
:debug:main libedit 20230828-3.1_0  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/libedit
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup muniversal 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl
:debug:main Sourcing PortGroup clang_dependency 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/clang_dependency-1.0.tcl
:debug:main muniversal: adding universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main No need to upgrade! libedit 20230828-3.1_0 >= libedit 20230828-3.1_0
:debug:main epoch: in tree: 0 installed: 0
:debug:main ncurses 6.5_0 exists in the ports tree
:debug:main ncurses 6.5_0  is the latest installed
:debug:main ncurses 6.5_0  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/ncurses
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup clang_dependency 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/clang_dependency-1.0.tcl
:debug:main adding the default universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main No need to upgrade! ncurses 6.5_0 >= ncurses 6.5_0
:debug:main epoch: in tree: 0 installed: 0
:debug:main libffi 3.4.6_1 exists in the ports tree
:debug:main libffi 3.4.6_1  is the latest installed
:debug:main libffi 3.4.6_1  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/libffi
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup muniversal 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl
:debug:main Sourcing PortGroup github 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/github-1.0.tcl
:debug:main Re-registering default for extract.rename
:debug:main Re-registering default for livecheck.url
:debug:main Re-registering default for livecheck.regex
:debug:main Re-registering default for extract.rename
:debug:main muniversal: adding universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main No need to upgrade! libffi 3.4.6_1 >= libffi 3.4.6_1
:debug:main epoch: in tree: 0 installed: 0
:debug:main sqlite3 3.46.0_0 exists in the ports tree
:debug:main sqlite3 3.46.0_0  is the latest installed
:debug:main sqlite3 3.46.0_0  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/databases/sqlite3
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup clang_dependency 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/clang_dependency-1.0.tcl
:debug:main adding the default universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main No need to upgrade! sqlite3 3.46.0_0 >= sqlite3 3.46.0_0
:debug:main epoch: in tree: 0 installed: 0
:debug:main openssl11 1.1.1w_1 exists in the ports tree
:debug:main openssl11 1.1.1w_1  is the latest installed
:debug:main openssl11 1.1.1w_1  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/openssl11
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup muniversal 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl
:debug:main muniversal: adding universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main No need to upgrade! openssl11 1.1.1w_1 >= openssl11 1.1.1w_1
:debug:main epoch: in tree: 0 installed: 0
:debug:main python_select 0.3_10 exists in the ports tree
:debug:main python_select 0.3_10  is the latest installed
:debug:main python_select 0.3_10  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/sysutils/python_select
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup select 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/select-1.0.tcl
:debug:main universal_variant is false, so not adding the default universal variant
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main No need to upgrade! python_select 0.3_10 >= python_select 0.3_10
:debug:main epoch: in tree: 0 installed: 0
:debug:main python2_select 0.1_0 exists in the ports tree
:debug:main python2_select 0.1_0  is the latest installed
:debug:main python2_select 0.1_0  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/sysutils/python2_select
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup select 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/select-1.0.tcl
:debug:main universal_variant is false, so not adding the default universal variant
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main No need to upgrade! python2_select 0.1_0 >= python2_select 0.1_0
:debug:main epoch: in tree: 0 installed: 0
:debug:main cython_select 0.1_2 exists in the ports tree
:debug:main cython_select 0.1_2  is the latest installed
:debug:main cython_select 0.1_2  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/python/cython_select
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup stub 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/stub-1.0.tcl
:debug:main Sourcing PortGroup select 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/select-1.0.tcl
:debug:main only one arch supported, so not adding the default universal variant
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Running callback stub::setup_stub
:debug:main Finished running callback stub::setup_stub
:debug:main No need to upgrade! cython_select 0.1_2 >= cython_select 0.1_2
:debug:main epoch: in tree: 0 installed: 0
:debug:main py27-oldest-supported-numpy 0.1_0 exists in the ports tree
:debug:main py27-oldest-supported-numpy 0.1_0  is the latest installed
:debug:main py27-oldest-supported-numpy 0.1_0  is active
:debug:main Merging existing requested variants '' into variants
:debug:main new fully merged portvariants: 
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/python/py-oldest-supported-numpy
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Re-registering default for distname
:debug:main Re-registering default for build.cmd
:debug:main Re-registering default for build.target
:debug:main Re-registering default for destroot.cmd
:debug:main Re-registering default for destroot.destdir
:debug:main Re-registering default for destroot.target
:debug:main Re-registering default for test.cmd
:debug:main Re-registering default for test.target
:debug:main Sourcing PortGroup python 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/python-1.0.tcl
:debug:main only one arch supported, so not adding the default universal variant
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Running callback python_add_dependencies
:debug:main Finished running callback python_add_dependencies
:debug:main No need to upgrade! py27-oldest-supported-numpy 0.1_0 >= py27-oldest-supported-numpy 0.1_0
:msg:main --->  Computing dependencies for py27-scipy:info:main .:debug:main py27-scipy has no conflicts
:debug:main Searching for dependency: swig-python
:debug:main Didn't find receipt, going to depspec regex for: swig-python
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/swig
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main only one arch supported, so not adding the default universal variant
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Searching for dependency: gcc13
:debug:main Didn't find receipt, going to depspec regex for: gcc13
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/lang/gcc13
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup select 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/select-1.0.tcl
:debug:main Sourcing PortGroup compiler_blacklist_versions 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compiler_blacklist_versions-1.0.tcl
:debug:main Sourcing PortGroup active_variants 1.1 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/active_variants-1.1.tcl
:debug:main Sourcing PortGroup conflicts_build 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/conflicts_build-1.0.tcl
:debug:main compiler clang 1500.3.9.4 not blacklisted because it doesn't match {clang < 800}
:debug:main compiler llvm-gcc-4.2 blacklisted because it's not installed or it doesn't work
:debug:main compiler clang 1500.3.9.4 not blacklisted because it doesn't match {clang < 1001}
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main universal variant already exists, so not adding the default one
:debug:main Executing variant stdlib_flag provides stdlib_flag
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Searching for dependency: py27-numpy
:debug:main Found Dependency: receipt exists for py27-numpy
:debug:main Searching for dependency: py27-pybind11
:debug:main Didn't find receipt, going to depspec regex for: py27-pybind11
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/python/py-pybind11
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Re-registering default for distname
:debug:main Re-registering default for build.cmd
:debug:main Re-registering default for build.target
:debug:main Re-registering default for destroot.cmd
:debug:main Re-registering default for destroot.destdir
:debug:main Re-registering default for destroot.target
:debug:main Re-registering default for test.cmd
:debug:main Re-registering default for test.target
:debug:main Sourcing PortGroup python 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/python-1.0.tcl
:debug:main only one arch supported, so not adding the default universal variant
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Running callback python_add_dependencies
:debug:main Finished running callback python_add_dependencies
:debug:main Searching for dependency: libgcc
:debug:main Found Dependency: receipt exists for libgcc
:debug:main Searching for dependency: OpenBLAS
:debug:main Didn't find receipt, going to depspec regex for: OpenBLAS
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/math/OpenBLAS
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Re-registering default for destroot.target
:debug:main Re-registering default for configure.dir
:debug:main Re-registering default for build.dir
:debug:main Re-registering default for configure.pre_args
:debug:main Sourcing PortGroup cmake 1.1 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/cmake-1.1.tcl
:debug:main Sourcing PortGroup active_variants 1.1 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/active_variants-1.1.tcl
:debug:main GCC versions for Darwin 23 arm - 10 11 12 13 devel
:debug:main Clang versions for Darwin 23 arm - 11 12 13 14 15 16 17 18 devel
:debug:main Sourcing PortGroup compilers 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compilers-1.0.tcl
:debug:main Sourcing PortGroup github 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/github-1.0.tcl
:debug:main Re-registering default for configure.cc_archflags
:debug:main Re-registering default for configure.objc_archflags
:debug:main Re-registering default for configure.cxx_archflags
:debug:main Re-registering default for configure.objcxx_archflags
:debug:main Re-registering default for configure.fc_archflags
:debug:main Re-registering default for configure.f90_archflags
:debug:main Re-registering default for configure.f77_archflags
:debug:main Re-registering default for configure.ld_archflags
:debug:main Re-registering default for configure.universal_cflags
:debug:main Re-registering default for configure.universal_objcflags
:debug:main Re-registering default for configure.universal_cxxflags
:debug:main Re-registering default for configure.universal_objcxxflags
:debug:main Re-registering default for configure.universal_cppflags
:debug:main Re-registering default for configure.universal_ldflags
:debug:main Sourcing PortGroup muniversal 1.1 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/muniversal-1.1.tcl
:debug:main Sourcing PortGroup xcode_workaround 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/xcode_workaround-1.0.tcl
:debug:main Re-registering default for extract.rename
:debug:main Re-registering default for livecheck.url
:debug:main Re-registering default for livecheck.regex
:debug:main Re-registering default for extract.rename
:debug:main muniversal: adding universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Executing variant gcc13 provides gcc13
:debug:main Executing variant lapack provides lapack
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Running callback compilers::add_fortran_legacy_support
:debug:main Finished running callback compilers::add_fortran_legacy_support
:debug:main Running callback muniversal::add_compiler_flags
:debug:main Finished running callback muniversal::add_compiler_flags
:debug:main Running callback xcode_workaround::xcode_workaround.appy_fix
:debug:main Finished running callback xcode_workaround::xcode_workaround.appy_fix
:debug:main Searching for dependency: python27
:debug:main Found Dependency: receipt exists for python27
:info:main .:debug:main swig-python has no conflicts
:debug:main Fetching swig-python-4.1.1_0.any_any.noarch.tbz2 archive size
:debug:main Searching for dependency: python_select
:debug:main Found Dependency: receipt exists for python_select
:debug:main Searching for dependency: swig
:debug:main Didn't find receipt, going to depspec regex for: swig
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/swig
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main adding the default universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:info:main .:debug:main swig has no conflicts
:debug:main Fetching swig-4.1.1_0.darwin_23.arm64.tbz2 archive size
:debug:main Searching for dependency: pcre2
:debug:main Found Dependency: receipt exists for pcre2
:info:main .:debug:main gcc13 has no conflicts
:debug:main Fetching gcc13-13.2.0_4+stdlib_flag.darwin_23.arm64.tbz2 archive size
:debug:main Searching for dependency: cctools
:debug:main Didn't find receipt, going to depspec regex for: cctools
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/cctools
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main universal_variant is false, so not adding the default universal variant
:debug:main Executing variant xcode provides xcode
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Searching for dependency: gmp
:debug:main Didn't find receipt, going to depspec regex for: gmp
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/gmp
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Re-registering default for configure.universal_args
:debug:main Re-registering default for configure.cc_archflags
:debug:main Re-registering default for configure.objc_archflags
:debug:main Re-registering default for configure.cxx_archflags
:debug:main Re-registering default for configure.objcxx_archflags
:debug:main Re-registering default for configure.fc_archflags
:debug:main Re-registering default for configure.f90_archflags
:debug:main Re-registering default for configure.f77_archflags
:debug:main Re-registering default for configure.ld_archflags
:debug:main Re-registering default for configure.universal_cflags
:debug:main Re-registering default for configure.universal_objcflags
:debug:main Re-registering default for configure.universal_cxxflags
:debug:main Re-registering default for configure.universal_objcxxflags
:debug:main Re-registering default for configure.universal_cppflags
:debug:main Re-registering default for configure.universal_ldflags
:debug:main Sourcing PortGroup muniversal 1.1 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/muniversal-1.1.tcl
:debug:main Sourcing PortGroup xcode_workaround 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/xcode_workaround-1.0.tcl
:debug:main muniversal: adding universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Running callback muniversal::add_compiler_flags
:debug:main Finished running callback muniversal::add_compiler_flags
:debug:main Running callback xcode_workaround::xcode_workaround.appy_fix
:debug:main Finished running callback xcode_workaround::xcode_workaround.appy_fix
:debug:main Searching for dependency: isl
:debug:main Didn't find receipt, going to depspec regex for: isl
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/isl
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup compiler_blacklist_versions 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compiler_blacklist_versions-1.0.tcl
:debug:main Re-registering default for configure.universal_args
:debug:main Re-registering default for configure.cc_archflags
:debug:main Re-registering default for configure.objc_archflags
:debug:main Re-registering default for configure.cxx_archflags
:debug:main Re-registering default for configure.objcxx_archflags
:debug:main Re-registering default for configure.fc_archflags
:debug:main Re-registering default for configure.f90_archflags
:debug:main Re-registering default for configure.f77_archflags
:debug:main Re-registering default for configure.ld_archflags
:debug:main Re-registering default for configure.universal_cflags
:debug:main Re-registering default for configure.universal_objcflags
:debug:main Re-registering default for configure.universal_cxxflags
:debug:main Re-registering default for configure.universal_objcxxflags
:debug:main Re-registering default for configure.universal_cppflags
:debug:main Re-registering default for configure.universal_ldflags
:debug:main Sourcing PortGroup muniversal 1.1 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/muniversal-1.1.tcl
:debug:main compiler clang 1500.3.9.4 not blacklisted because it doesn't match {clang < 500}
:debug:main muniversal: adding universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Running callback muniversal::add_compiler_flags
:debug:main Finished running callback muniversal::add_compiler_flags
:debug:main Searching for dependency: ld64
:debug:main Didn't find receipt, going to depspec regex for: ld64
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/ld64
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup compiler_blacklist_versions 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compiler_blacklist_versions-1.0.tcl
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main universal variant already exists, so not adding the default one
:debug:main Executing variant ld64_xcode provides ld64_xcode
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Searching for dependency: libiconv
:debug:main Found Dependency: receipt exists for libiconv
:debug:main Searching for dependency: libmpc
:debug:main Didn't find receipt, going to depspec regex for: libmpc
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/libmpc
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main adding the default universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Searching for dependency: mpfr
:debug:main Didn't find receipt, going to depspec regex for: mpfr
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/mpfr
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup muniversal 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl
:debug:main Sourcing PortGroup compiler_blacklist_versions 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compiler_blacklist_versions-1.0.tcl
:debug:main Sourcing PortGroup xcode_workaround 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/xcode_workaround-1.0.tcl
:debug:main compiler clang 1500.3.9.4 not blacklisted because it doesn't match {clang == 211.10.1}
:debug:main muniversal: adding universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Running callback xcode_workaround::xcode_workaround.appy_fix
:debug:main Finished running callback xcode_workaround::xcode_workaround.appy_fix
:debug:main Searching for dependency: zlib
:debug:main Found Dependency: receipt exists for zlib
:debug:main Searching for dependency: zstd
:debug:main Didn't find receipt, going to depspec regex for: zstd
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/archivers/zstd
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup github 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/github-1.0.tcl
:debug:main Sourcing PortGroup clang_dependency 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/clang_dependency-1.0.tcl
:debug:main Sourcing PortGroup compiler_wrapper 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compiler_wrapper-1.0.tcl
:debug:main Re-registering default for compwrap.add_compiler_flags
:debug:main Re-registering default for use_configure
:debug:main Re-registering default for universal_variant
:debug:main Sourcing PortGroup makefile 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/makefile-1.0.tcl
:debug:main Re-registering default for configure.universal_args
:debug:main Re-registering default for configure.cc_archflags
:debug:main Re-registering default for configure.objc_archflags
:debug:main Re-registering default for configure.cxx_archflags
:debug:main Re-registering default for configure.objcxx_archflags
:debug:main Re-registering default for configure.fc_archflags
:debug:main Re-registering default for configure.f90_archflags
:debug:main Re-registering default for configure.f77_archflags
:debug:main Re-registering default for configure.ld_archflags
:debug:main Re-registering default for configure.universal_cflags
:debug:main Re-registering default for configure.universal_objcflags
:debug:main Re-registering default for configure.universal_cxxflags
:debug:main Re-registering default for configure.universal_objcxxflags
:debug:main Re-registering default for configure.universal_cppflags
:debug:main Re-registering default for configure.universal_ldflags
:debug:main Sourcing PortGroup muniversal 1.1 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/muniversal-1.1.tcl
:debug:main Re-registering default for extract.rename
:debug:main Re-registering default for livecheck.url
:debug:main Re-registering default for livecheck.regex
:debug:main Re-registering default for extract.rename
:debug:main muniversal: adding universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Running callback compwrap::configure_envs
:debug:main Finished running callback compwrap::configure_envs
:debug:main Running callback makefile_pg::makefile_setup
:debug:main Finished running callback makefile_pg::makefile_setup
:debug:main Running callback muniversal::add_compiler_flags
:debug:main Finished running callback muniversal::add_compiler_flags
:debug:main Searching for dependency: gcc_select
:debug:main Didn't find receipt, going to depspec regex for: gcc_select
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/sysutils/gcc_select
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup stub 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/stub-1.0.tcl
:debug:main Sourcing PortGroup select 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/select-1.0.tcl
:debug:main only one arch supported, so not adding the default universal variant
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Running callback stub::setup_stub
:debug:main Finished running callback stub::setup_stub
:debug:main Searching for dependency: gcc13-libcxx
:debug:main Didn't find receipt, going to depspec regex for: gcc13-libcxx
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/lang/gcc13
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup select 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/select-1.0.tcl
:debug:main Sourcing PortGroup compiler_blacklist_versions 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compiler_blacklist_versions-1.0.tcl
:debug:main Sourcing PortGroup active_variants 1.1 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/active_variants-1.1.tcl
:debug:main Sourcing PortGroup conflicts_build 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/conflicts_build-1.0.tcl
:debug:main PortGroup active_variants 1.1 included previously, not sourcing again
:debug:main GCC versions for Darwin 23 arm - 10 11 12 13 devel
:debug:main Clang versions for Darwin 23 arm - 11 12 13 14 15 16 17 18 devel
:debug:main Sourcing PortGroup compilers 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compilers-1.0.tcl
:debug:main Compiler clang34 not available for Darwin23 arm
:debug:main Compiler clang35 not available for Darwin23 arm
:debug:main Compiler clang36 not available for Darwin23 arm
:debug:main Compiler clang37 not available for Darwin23 arm
:debug:main Compiler clang50 not available for Darwin23 arm
:debug:main Compiler clang60 not available for Darwin23 arm
:debug:main Compiler clang70 not available for Darwin23 arm
:debug:main Compiler clang80 not available for Darwin23 arm
:debug:main Compiler clang90 not available for Darwin23 arm
:debug:main compiler clang 1500.3.9.4 not blacklisted because it doesn't match {clang < 800}
:debug:main compiler llvm-gcc-4.2 blacklisted because it's not installed or it doesn't work
:debug:main compiler clang 1500.3.9.4 not blacklisted because it doesn't match {clang < 1001}
:debug:main universal_variant is false, so not adding the default universal variant
:debug:main Executing variant clang16 provides clang16
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Running callback compilers::add_fortran_legacy_support
:debug:main Finished running callback compilers::add_fortran_legacy_support
:info:main .:debug:main cctools has no conflicts
:debug:main Fetching cctools-949.0.1_3+xcode.darwin_any.noarch.tbz2 archive size
:info:main .:debug:main gmp has no conflicts
:debug:main Fetching gmp-6.3.0_0.darwin_23.arm64.tbz2 archive size
:info:main .:debug:main Checking for conflicts against isl
:debug:main Searching for dependency: isl-devel
:debug:main Didn't find receipt, going to depspec regex for: isl-devel
:debug:main Fetching isl-0.24_1.darwin_23.arm64.tbz2 archive size
:info:main .:debug:main ld64 has no conflicts
:debug:main Fetching ld64-3_6+ld64_xcode.darwin_23.arm64.tbz2 archive size
:debug:main Searching for dependency: ld64-xcode
:debug:main Didn't find receipt, going to depspec regex for: ld64-xcode
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/devel/ld64
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup compiler_blacklist_versions 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/compiler_blacklist_versions-1.0.tcl
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main universal variant already exists, so not adding the default one
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:info:main .:debug:main ld64-xcode has no conflicts
:debug:main Fetching ld64-xcode-2_6.darwin_23.arm64.tbz2 archive size
:info:main .:debug:main libmpc has no conflicts
:debug:main Fetching libmpc-1.3.1_0.darwin_23.arm64.tbz2 archive size
:info:main .:debug:main mpfr has no conflicts
:debug:main Fetching mpfr-4.2.1_0.darwin_23.arm64.tbz2 archive size
:info:main .:debug:main zstd has no conflicts
:debug:main Fetching zstd-1.5.6_0.darwin_23.arm64.tbz2 archive size
:debug:main Searching for dependency: lz4
:debug:main Didn't find receipt, going to depspec regex for: lz4
:debug:main Opening port in directory: /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/archivers/lz4
:debug:main OS darwin/23.5.0 (macOS 14.5) arch arm
:debug:main Sourcing PortGroup github 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/github-1.0.tcl
:debug:main Sourcing PortGroup muniversal 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/muniversal-1.0.tcl
:debug:main Sourcing PortGroup clang_dependency 1.0 from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/group/clang_dependency-1.0.tcl
:debug:main Re-registering default for extract.rename
:debug:main Re-registering default for livecheck.url
:debug:main Re-registering default for livecheck.regex
:debug:main Re-registering default for extract.rename
:debug:main muniversal: adding universal variant
:debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/_resources/port1.0/variant_descriptions.conf
:debug:main Running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies
:debug:main Running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies
:debug:main Running callback portstartupitem::add_notes
:debug:main Finished running callback portstartupitem::add_notes
:debug:main Searching for dependency: xz
:debug:main Found Dependency: receipt exists for xz
:info:main .:debug:main lz4 has no conflicts
:debug:main Fetching lz4-1.9.4_0.darwin_23.arm64.tbz2 archive size
:info:main .:debug:main gcc_select has no conflicts
:debug:main Fetching gcc_select-0.1_10.darwin_23.noarch.tbz2 archive size
:info:main .:debug:main gcc13-libcxx has no conflicts
:debug:main Fetching gcc13-libcxx-13.2.0_4+clang16.any_any.noarch.tbz2 archive size
:info:main .:debug:main py27-pybind11 has no conflicts
:debug:main Fetching py27-pybind11-2.4.3_0.darwin_any.noarch.tbz2 archive size
:info:main .:debug:main Checking for conflicts against OpenBLAS
:debug:main Searching for dependency: OpenBLAS-devel
:debug:main Didn't find receipt, going to depspec regex for: OpenBLAS-devel
:debug:main Fetching OpenBLAS-0.3.25_6+gcc13+lapack.darwin_23.arm64.tbz2 archive size
:debug:main Executing org.macports.main (py27-scipy)
:debug:main dropping privileges: euid changed to 502, egid changed to 501.
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:archivefetch archivefetch phase started at Sat Jun  1 22:43:53 +04 2024
:msg:archivefetch --->  Fetching archive for py27-scipy
:debug:archivefetch Executing proc-pre-org.macports.archivefetch-archivefetch-0
:debug:archivefetch Executing org.macports.archivefetch (py27-scipy)
:debug:archivefetch euid/egid changed to: 0/0
:debug:archivefetch chowned /opt/local/var/macports/incoming to macports
:debug:archivefetch euid/egid changed to: 502/501
:info:archivefetch --->  py27-scipy-1.2.3_1+gfortran+openblas.darwin_23.arm64.tbz2 doesn't seem to exist in /opt/local/var/macports/incoming/verified
:msg:archivefetch --->  Attempting to fetch py27-scipy-1.2.3_1+gfortran+openblas.darwin_23.arm64.tbz2 from https://packages.macports.org/py27-scipy
:debug:archivefetch Fetching archive failed: The requested URL returned error: 404
:msg:archivefetch --->  Attempting to fetch py27-scipy-1.2.3_1+gfortran+openblas.darwin_23.arm64.tbz2 from http://jog.id.packages.macports.org/macports/packages/py27-scipy
:debug:archivefetch Fetching archive failed: The requested URL returned error: 404
:msg:archivefetch --->  Attempting to fetch py27-scipy-1.2.3_1+gfortran+openblas.darwin_23.arm64.tbz2 from https://cph.dk.packages.macports.org/py27-scipy
:debug:archivefetch Fetching archive failed: The requested URL returned error: 404
:debug:archivefetch Privilege de-escalation not attempted as not running as root.
:debug:fetch fetch phase started at Sat Jun  1 22:43:56 +04 2024
:notice:fetch --->  Fetching distfiles for py27-scipy
:debug:fetch Executing proc-pre-org.macports.fetch-fetch-0
:debug:fetch Executing org.macports.fetch (py27-scipy)
:debug:fetch Privilege de-escalation not attempted as not running as root.
:debug:checksum checksum phase started at Sat Jun  1 22:43:56 +04 2024
:notice:checksum --->  Verifying checksums for py27-scipy
:debug:checksum Executing org.macports.checksum (py27-scipy)
:info:checksum --->  Checksumming scipy-1.2.3.tar.gz
:debug:checksum Calculated (rmd160) is 868076b4d88257a6b536f4c3a4e1e8230b587290
:debug:checksum Correct (rmd160) checksum for scipy-1.2.3.tar.gz
:debug:checksum Calculated (sha256) is beb6123e91a0bdfba4557b6560be4899dac174a38c30876e5cfc60382ecb4ff7
:debug:checksum Correct (sha256) checksum for scipy-1.2.3.tar.gz
:debug:checksum Calculated (size) is 18564471
:debug:checksum Correct (size) checksum for scipy-1.2.3.tar.gz
:debug:checksum Privilege de-escalation not attempted as not running as root.
:debug:extract extract phase started at Sat Jun  1 22:43:57 +04 2024
:notice:extract --->  Extracting py27-scipy
:debug:extract Executing org.macports.extract (py27-scipy)
:info:extract --->  Extracting scipy-1.2.3.tar.gz
:debug:extract setting option extract.args to '/opt/local/var/macports/distfiles/py27-scipy/scipy-1.2.3.tar.gz'
:debug:extract Environment: 
:debug:extract CC_PRINT_OPTIONS='YES'
:debug:extract CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/.CC_PRINT_OPTIONS'
:debug:extract CPATH='/opt/local/include'
:debug:extract DEVELOPER_DIR='/Library/Developer/CommandLineTools'
:debug:extract LIBRARY_PATH='/opt/local/lib'
:debug:extract MACOSX_DEPLOYMENT_TARGET='14.0'
:debug:extract SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk'
:info:extract Executing:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work" && /usr/bin/gzip -dc '/opt/local/var/macports/distfiles/py27-scipy/scipy-1.2.3.tar.gz' | /usr/bin/tar -xf - 
:debug:extract system:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work" && /usr/bin/gzip -dc '/opt/local/var/macports/distfiles/py27-scipy/scipy-1.2.3.tar.gz' | /usr/bin/tar -xf - 
:debug:extract euid/egid changed to: 0/0
:debug:extract chowned /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work to macports
:debug:extract euid/egid changed to: 502/501
:debug:extract extract.rename: Renaming scipy-scipy-3a9525f -> scipy-1.2.3
:debug:extract Executing proc-post-org.macports.extract-extract-0
:debug:extract Privilege de-escalation not attempted as not running as root.
:debug:patch patch phase started at Sat Jun  1 22:43:57 +04 2024
:debug:patch Executing org.macports.patch (py27-scipy)
:notice:patch --->  Applying patches to py27-scipy
:info:patch --->  Applying patch-xcode12-fixes.27.diff
:debug:patch Environment: 
:debug:patch CC_PRINT_OPTIONS='YES'
:debug:patch CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/.CC_PRINT_OPTIONS'
:debug:patch CPATH='/opt/local/include'
:debug:patch DEVELOPER_DIR='/Library/Developer/CommandLineTools'
:debug:patch LIBRARY_PATH='/opt/local/lib'
:debug:patch MACOSX_DEPLOYMENT_TARGET='14.0'
:debug:patch SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk'
:info:patch Executing:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/scipy-1.2.3" && /usr/bin/patch -p1 < '/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/python/py27-scipy/files/patch-xcode12-fixes.27.diff'
:debug:patch system:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/scipy-1.2.3" && /usr/bin/patch -p1 < '/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/python/py27-scipy/files/patch-xcode12-fixes.27.diff'
:info:patch patching file 'scipy/sparse/linalg/dsolve/SuperLU/SRC/clacon2.c'
:info:patch patching file 'scipy/sparse/linalg/dsolve/SuperLU/SRC/dmach.c'
:info:patch patching file 'scipy/sparse/linalg/dsolve/SuperLU/SRC/ilu_cdrop_row.c'
:info:patch patching file 'scipy/sparse/linalg/dsolve/SuperLU/SRC/ilu_zdrop_row.c'
:info:patch patching file 'scipy/sparse/linalg/dsolve/SuperLU/SRC/slacon2.c'
:info:patch patching file 'scipy/sparse/linalg/dsolve/SuperLU/SRC/smach.c'
:info:patch patching file 'scipy/sparse/linalg/dsolve/SuperLU/SRC/sp_ienv.c'
:info:patch patching file 'scipy/sparse/linalg/dsolve/SuperLU/SRC/zlacon2.c'
:info:patch patching file 'scipy/cluster/_vq.pyx'
:info:patch patching file 'scipy/interpolate/_ppoly.pyx'
:info:patch patching file 'scipy/spatial/qhull.pyx'
:debug:patch Privilege de-escalation not attempted as not running as root.
:debug:configure configure phase started at Sat Jun  1 22:43:57 +04 2024
:notice:configure --->  Configuring py27-scipy
:debug:configure Preferred compilers: clang macports-clang-16 macports-clang-15 macports-clang-14 macports-clang-11
:debug:configure Using compiler 'Xcode Clang'
:debug:configure Executing proc-pre-org.macports.configure-configure-0
:debug:configure Active variants check for source-type install considers depends_fetch depends_extract depends_lib depends_build depends_run: py27-numpy py27-pybind11 libgcc OpenBLAS python27 swig-python gcc13
:debug:configure Executing proc-pre-org.macports.configure-configure-1
:debug:configure compilers.enforce_c list: 
:debug:configure compilers.enforce_fortran list: 
:debug:configure compilers.enforce_some_fortran list: 
:debug:configure compilers PG: RPATH added to ldflags as GCC version is 13
:debug:configure Executing proc-pre-org.macports.configure-configure-2
:debug:configure Executing org.macports.configure (py27-scipy)
:debug:configure Executing portconfigure::configure_finish
:debug:configure Privilege de-escalation not attempted as not running as root.
:debug:build build phase started at Sat Jun  1 22:43:57 +04 2024
:notice:build --->  Building py27-scipy
:debug:build Executing proc-pre-org.macports.build-build-0
:debug:build Executing org.macports.build (py27-scipy)
:debug:build Environment: 
:debug:build ATLAS='None'
:debug:build CC='/usr/bin/clang'
:debug:build CCFLAGS='-I/opt/local/include -L/opt/local/lib'
:debug:build CC_PRINT_OPTIONS='YES'
:debug:build CC_PRINT_OPTIONS_FILE='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/.CC_PRINT_OPTIONS'
:debug:build CFLAGS='-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk'
:debug:build CPATH='/opt/local/include'
:debug:build CPPFLAGS='-I/opt/local/include'
:debug:build CXX='/usr/bin/clang++'
:debug:build CXXFLAGS='-stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk'
:debug:build DEVELOPER_DIR='/Library/Developer/CommandLineTools'
:debug:build F77='/opt/local/bin/gfortran-mp-13'
:debug:build F90='/opt/local/bin/gfortran-mp-13'
:debug:build FC='/opt/local/bin/gfortran-mp-13'
:debug:build LIBRARY_PATH='/opt/local/lib'
:debug:build MACOSX_DEPLOYMENT_TARGET='14.0'
:debug:build MKLROOT='None'
:debug:build OBJC='/usr/bin/clang'
:debug:build OBJCFLAGS='-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk'
:debug:build OPENBLAS='/opt/local/lib'
:debug:build SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX14.sdk'
:debug:build SETUPTOOLS_USE_DISTUTILS='stdlib'
:info:build Executing:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/scipy-1.2.3" && /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 setup.py --no-user-cfg config_fc --fcompiler gnu95 --f77exec /opt/local/bin/gfortran-mp-13 --f77flags='-m64 -Os -fno-second-underscore -fallow-argument-mismatch' --f90exec /opt/local/bin/gfortran-mp-13 --f90flags='-m64 -Os -fno-second-underscore -fallow-argument-mismatch' config --cc /usr/bin/clang --include-dirs /opt/local/include --library-dirs /opt/local/lib build 
:debug:build system:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/scipy-1.2.3" && /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 setup.py --no-user-cfg config_fc --fcompiler gnu95 --f77exec /opt/local/bin/gfortran-mp-13 --f77flags='-m64 -Os -fno-second-underscore -fallow-argument-mismatch' --f90exec /opt/local/bin/gfortran-mp-13 --f90flags='-m64 -Os -fno-second-underscore -fallow-argument-mismatch' config --cc /usr/bin/clang --include-dirs /opt/local/include --library-dirs /opt/local/lib build 
:info:build Running scipy/linalg/_generate_pyx.py
:info:build Running scipy/special/_generate_pyx.py
:info:build Processing scipy/cluster/_vq.pyx
:info:build Processing scipy/cluster/_optimal_leaf_ordering.pyx
:info:build Processing scipy/cluster/_hierarchy.pyx
:info:build Processing scipy/ndimage/src/_cytest.pyx
:info:build Processing scipy/ndimage/src/_ni_label.pyx
:info:build Processing scipy/linalg/cython_lapack.pyx
:info:build Processing scipy/linalg/_solve_toeplitz.pyx
:info:build Processing scipy/linalg/cython_blas.pyx
:info:build /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/Cython/Compiler/Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/scipy-1.2.3/scipy/cluster/_optimal_leaf_ordering.pyx
:info:build   tree = Parsing.p_module(s, pxd, full_module_name)
:info:build /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/Cython/Compiler/Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/scipy-1.2.3/scipy/cluster/_hierarchy.pyx
:info:build   tree = Parsing.p_module(s, pxd, full_module_name)
:info:build /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/Cython/Compiler/Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/scipy-1.2.3/scipy/ndimage/src/_cytest.pxd
:info:build   tree = Parsing.p_module(s, pxd, full_module_name)
:info:build /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/Cython/Compiler/Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/scipy-1.2.3/scipy/linalg/cython_blas.pxd
:info:build   tree = Parsing.p_module(s, pxd, full_module_name)
:info:build /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/Cython/Compiler/Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/scipy-1.2.3/scipy/cluster/_vq.pyx
:info:build   tree = Parsing.p_module(s, pxd, full_module_name)
:info:build /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/Cython/Compiler/Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/scipy-1.2.3/scipy/ndimage/src/_ni_label.pyx
:info:build   tree = Parsing.p_module(s, pxd, full_module_name)
:info:build /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/Cython/Compiler/Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/scipy-1.2.3/scipy/linalg/cython_lapack.pxd
:info:build   tree = Parsing.p_module(s, pxd, full_module_name)
:info:build /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/Cython/Compiler/Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/scipy-1.2.3/scipy/linalg/_solve_toeplitz.pyx
:info:build   tree = Parsing.p_module(s, pxd, full_module_name)
:info:build warning: cython_blas.pyx:1031:46: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
:info:build Error compiling Cython file:
:info:build ------------------------------------------------------------
:info:build ...
:info:build     if with_signature:
:info:build         signature = "int (double *, npy_intp, double *, npy_intp, void *)"
:info:build     try:
:info:build         capsule = PyCapsule_New(<void *>_filter1d, signature, _destructor)
:info:build                                                               ^
:info:build ------------------------------------------------------------
:info:build _cytest.pyx:46:62: Cannot assign type 'void (object) except *' to 'PyCapsule_Destructor' (alias of 'void (*)(object) noexcept'). Exception values are incompatible. Suggest adding 'noexcept' to the type of '_destructor'.
:info:build performance hint: _ni_label.pyx:58:5: Exception check on 'fused_nonzero_line' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'fused_nonzero_line' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'fused_nonzero_line' to allow an error code to be returned.
:info:build performance hint: _ni_label.pyx:70:5: Exception check on 'fused_read_line' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'fused_read_line' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'fused_read_line' to allow an error code to be returned.
:info:build Traceback (most recent call last):
:info:build Processing scipy/linalg/_decomp_update.pyx.in
:info:build   File "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/scipy-1.2.3/tools/cythonize.py", line 306, in <module>
:info:build     main()
:info:build   File "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/scipy-1.2.3/tools/cythonize.py", line 302, in main
:info:build     find_process_files(root_dir)
:info:build   File "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/scipy-1.2.3/tools/cythonize.py", line 291, in find_process_files
:info:build     for result in pool.imap_unordered(lambda args: process(*args), jobs):
:info:build   File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/multiprocessing/pool.py", line 673, in next
:info:build     raise value
:info:build Exception: Cython either isn't installed or it failed.
:info:build Error compiling Cython file:
:info:build ------------------------------------------------------------
:info:build ...
:info:build     else:
:info:build         # Determine the pivot using the median-of-three rule.
:info:build         # The smallest of the three is moved to the beginning of the array,
:info:build         # the middle (the pivot value) is moved to the end, and the largest
:info:build         # is moved to the pivot index.
:info:build         pivot_idx = size / 2
:info:build                          ^
:info:build ------------------------------------------------------------
:info:build _optimal_leaf_ordering.pyx:91:25: Cannot assign type 'double' to 'int'
:info:build performance hint: cython_blas.pyx:194:5: Exception check on 'cdotc' will always require the GIL to be acquired. Declare 'cdotc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: cython_blas.pyx:202:5: Exception check on 'cdotu' will always require the GIL to be acquired. Declare 'cdotu' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: cython_blas.pxd:90:12: No exception value declared for 'dasum' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pxd:94:13: No exception value declared for 'dcabs1' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pxd:98:11: No exception value declared for 'ddot' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pxd:108:12: No exception value declared for 'dnrm2' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pxd:122:12: No exception value declared for 'dsdot' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pxd:160:13: No exception value declared for 'dzasum' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pxd:162:13: No exception value declared for 'dznrm2' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pxd:164:15: No exception value declared for 'icamax' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pxd:166:15: No exception value declared for 'idamax' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pxd:168:15: No exception value declared for 'isamax' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pxd:170:15: No exception value declared for 'izamax' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pxd:172:15: No exception value declared for 'lsame' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pxd:174:12: No exception value declared for 'sasum' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pxd:178:13: No exception value declared for 'scasum' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pxd:180:13: No exception value declared for 'scnrm2' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pxd:184:11: No exception value declared for 'sdot' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pxd:186:13: No exception value declared for 'sdsdot' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pxd:196:12: No exception value declared for 'snrm2' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_blas.pyx:354:5: Exception check on 'zdotc' will always require the GIL to be acquired. Declare 'zdotc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: cython_blas.pyx:362:5: Exception check on 'zdotu' will always require the GIL to be acquired. Declare 'zdotu' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: cython_blas.pyx:369:5: Exception check on 'caxpy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'caxpy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'caxpy' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:374:5: Exception check on 'ccopy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ccopy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ccopy' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:379:5: Exception check on 'cgbmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgbmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgbmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:384:5: Exception check on 'cgemm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgemm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgemm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:389:5: Exception check on 'cgemv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgemv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgemv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:394:5: Exception check on 'cgerc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgerc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgerc' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:399:5: Exception check on 'cgeru' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgeru' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgeru' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:404:5: Exception check on 'chbmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chbmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chbmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:409:5: Exception check on 'chemm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chemm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chemm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:414:5: Exception check on 'chemv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chemv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chemv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:419:5: Exception check on 'cher' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cher' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cher' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:424:5: Exception check on 'cher2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cher2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cher2' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:429:5: Exception check on 'cher2k' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cher2k' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cher2k' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:434:5: Exception check on 'cherk' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cherk' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cherk' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:439:5: Exception check on 'chpmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chpmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chpmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:444:5: Exception check on 'chpr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chpr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chpr' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:449:5: Exception check on 'chpr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chpr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chpr2' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:454:5: Exception check on 'crotg' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'crotg' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'crotg' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:459:5: Exception check on 'cscal' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cscal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cscal' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:464:5: Exception check on 'csrot' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csrot' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csrot' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:469:5: Exception check on 'csscal' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csscal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csscal' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:474:5: Exception check on 'cswap' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cswap' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cswap' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:479:5: Exception check on 'csymm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csymm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csymm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:484:5: Exception check on 'csyr2k' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csyr2k' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csyr2k' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:489:5: Exception check on 'csyrk' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csyrk' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csyrk' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:494:5: Exception check on 'ctbmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctbmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctbmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:499:5: Exception check on 'ctbsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctbsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctbsv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:504:5: Exception check on 'ctpmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctpmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctpmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:509:5: Exception check on 'ctpsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctpsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctpsv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:514:5: Exception check on 'ctrmm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctrmm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctrmm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:519:5: Exception check on 'ctrmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctrmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctrmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:524:5: Exception check on 'ctrsm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctrsm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctrsm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:529:5: Exception check on 'ctrsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctrsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctrsv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:534:5: Exception check on 'daxpy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'daxpy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'daxpy' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:539:5: Exception check on 'dcopy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dcopy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dcopy' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:544:5: Exception check on 'dgbmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgbmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgbmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:549:5: Exception check on 'dgemm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgemm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgemm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:554:5: Exception check on 'dgemv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgemv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgemv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:559:5: Exception check on 'dger' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dger' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dger' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:564:5: Exception check on 'drot' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'drot' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'drot' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:569:5: Exception check on 'drotg' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'drotg' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'drotg' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:574:5: Exception check on 'drotm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'drotm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'drotm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:579:5: Exception check on 'drotmg' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'drotmg' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'drotmg' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:584:5: Exception check on 'dsbmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsbmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsbmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:589:5: Exception check on 'dscal' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dscal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dscal' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:594:5: Exception check on 'dspmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dspmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dspmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:599:5: Exception check on 'dspr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dspr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dspr' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:604:5: Exception check on 'dspr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dspr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dspr2' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:609:5: Exception check on 'dswap' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dswap' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dswap' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:614:5: Exception check on 'dsymm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsymm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsymm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:619:5: Exception check on 'dsymv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsymv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsymv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:624:5: Exception check on 'dsyr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsyr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsyr' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:629:5: Exception check on 'dsyr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsyr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsyr2' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:634:5: Exception check on 'dsyr2k' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsyr2k' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsyr2k' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:639:5: Exception check on 'dsyrk' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsyrk' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsyrk' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:644:5: Exception check on 'dtbmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtbmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtbmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:649:5: Exception check on 'dtbsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtbsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtbsv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:654:5: Exception check on 'dtpmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtpmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtpmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:659:5: Exception check on 'dtpsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtpsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtpsv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:664:5: Exception check on 'dtrmm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtrmm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtrmm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:669:5: Exception check on 'dtrmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtrmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtrmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:674:5: Exception check on 'dtrsm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtrsm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtrsm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:679:5: Exception check on 'dtrsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtrsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtrsv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:684:5: Exception check on 'saxpy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'saxpy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'saxpy' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:689:5: Exception check on 'scopy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'scopy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'scopy' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:694:5: Exception check on 'sgbmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgbmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgbmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:699:5: Exception check on 'sgemm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgemm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgemm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:704:5: Exception check on 'sgemv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgemv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgemv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:709:5: Exception check on 'sger' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sger' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sger' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:714:5: Exception check on 'srot' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'srot' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'srot' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:719:5: Exception check on 'srotg' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'srotg' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'srotg' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:724:5: Exception check on 'srotm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'srotm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'srotm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:729:5: Exception check on 'srotmg' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'srotmg' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'srotmg' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:734:5: Exception check on 'ssbmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssbmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssbmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:739:5: Exception check on 'sscal' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sscal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sscal' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:744:5: Exception check on 'sspmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sspmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sspmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:749:5: Exception check on 'sspr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sspr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sspr' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:754:5: Exception check on 'sspr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sspr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sspr2' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:759:5: Exception check on 'sswap' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sswap' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sswap' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:764:5: Exception check on 'ssymm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssymm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssymm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:769:5: Exception check on 'ssymv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssymv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssymv' to allow an error code to be returned.
:info:build Cythonizing sources
:info:build Traceback (most recent call last):
:info:build   File "setup.py", line 492, in <module>
:info:build performance hint: cython_blas.pyx:774:5: Exception check on 'ssyr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssyr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssyr' to allow an error code to be returned.
:info:build     setup_package()
:info:build   File "setup.py", line 476, in setup_package
:info:build performance hint: cython_blas.pyx:779:5: Exception check on 'ssyr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssyr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssyr2' to allow an error code to be returned.
:info:build     generate_cython()
:info:build   File "setup.py", line 253, in generate_cython
:info:build     raise RuntimeError("Running cythonize failed!")
:info:build RuntimeError: Running cythonize failed!
:info:build performance hint: cython_blas.pyx:784:5: Exception check on 'ssyr2k' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssyr2k' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssyr2k' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:789:5: Exception check on 'ssyrk' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssyrk' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssyrk' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:794:5: Exception check on 'stbmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stbmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stbmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:799:5: Exception check on 'stbsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stbsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stbsv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:804:5: Exception check on 'stpmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stpmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stpmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:809:5: Exception check on 'stpsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stpsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stpsv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:814:5: Exception check on 'strmm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'strmm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'strmm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:819:5: Exception check on 'strmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'strmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'strmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:824:5: Exception check on 'strsm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'strsm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'strsm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:829:5: Exception check on 'strsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'strsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'strsv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:834:5: Exception check on 'zaxpy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zaxpy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zaxpy' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:839:5: Exception check on 'zcopy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zcopy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zcopy' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:844:5: Exception check on 'zdrot' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zdrot' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zdrot' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:849:5: Exception check on 'zdscal' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zdscal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zdscal' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:854:5: Exception check on 'zgbmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgbmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgbmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:859:5: Exception check on 'zgemm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgemm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgemm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:864:5: Exception check on 'zgemv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgemv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgemv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:869:5: Exception check on 'zgerc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgerc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgerc' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:874:5: Exception check on 'zgeru' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgeru' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgeru' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:879:5: Exception check on 'zhbmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhbmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhbmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:884:5: Exception check on 'zhemm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhemm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhemm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:889:5: Exception check on 'zhemv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhemv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhemv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:894:5: Exception check on 'zher' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zher' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zher' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:899:5: Exception check on 'zher2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zher2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zher2' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:904:5: Exception check on 'zher2k' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zher2k' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zher2k' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:909:5: Exception check on 'zherk' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zherk' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zherk' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:914:5: Exception check on 'zhpmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhpmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhpmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:919:5: Exception check on 'zhpr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhpr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhpr' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:924:5: Exception check on 'zhpr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhpr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhpr2' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:929:5: Exception check on 'zrotg' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zrotg' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zrotg' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:934:5: Exception check on 'zscal' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zscal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zscal' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:939:5: Exception check on 'zswap' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zswap' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zswap' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:944:5: Exception check on 'zsymm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsymm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsymm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:949:5: Exception check on 'zsyr2k' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsyr2k' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsyr2k' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:954:5: Exception check on 'zsyrk' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsyrk' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsyrk' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:959:5: Exception check on 'ztbmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztbmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztbmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:964:5: Exception check on 'ztbsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztbsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztbsv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:969:5: Exception check on 'ztpmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztpmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztpmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:974:5: Exception check on 'ztpsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztpsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztpsv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:979:5: Exception check on 'ztrmm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztrmm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztrmm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:984:5: Exception check on 'ztrmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztrmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztrmv' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:989:5: Exception check on 'ztrsm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztrsm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztrsm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:994:5: Exception check on 'ztrsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztrsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztrsv' to allow an error code to be returned.
:info:build Error compiling Cython file:
:info:build ------------------------------------------------------------
:info:build ...
:info:build     iti = <PyArrayIterObject *> _iti
:info:build     itstruct = <PyArrayIterObject *> _itstruct
:info:build     # we only process this many neighbors from the itstruct iterator before
:info:build     # reaching the center, where we stop
:info:build     num_neighbors = (structure.size / 3) // 2
:info:build                                          ^
:info:build ------------------------------------------------------------
:info:build _ni_label.pyx:274:41: Cannot assign type 'double' to 'int'
:info:build performance hint: cython_blas.pyx:1003:6: Exception check on '_test_cdotc' will always require the GIL to be acquired. Declare '_test_cdotc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: cython_blas.pyx:1010:6: Exception check on '_test_cdotu' will always require the GIL to be acquired. Declare '_test_cdotu' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: cython_blas.pyx:1182:6: Exception check on '_test_zdotc' will always require the GIL to be acquired. Declare '_test_zdotc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: cython_blas.pyx:1189:6: Exception check on '_test_zdotu' will always require the GIL to be acquired. Declare '_test_zdotu' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: cython_blas.pyx:1008:16: Exception check after calling 'cdotc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cdotc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Declare any exception value explicitly for functions in pxd files.
:info:build performance hint: cython_blas.pyx:1015:16: Exception check after calling 'cdotu' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cdotu' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Declare any exception value explicitly for functions in pxd files.
:info:build performance hint: cython_blas.pyx:1071:13: Exception check after calling 'dgemm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgemm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgemm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:1102:13: Exception check after calling 'dgemm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgemm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgemm' to allow an error code to be returned.
:info:build performance hint: cython_blas.pyx:1187:16: Exception check after calling 'zdotc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zdotc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Declare any exception value explicitly for functions in pxd files.
:info:build performance hint: cython_blas.pyx:1194:16: Exception check after calling 'zdotu' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zdotu' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Declare any exception value explicitly for functions in pxd files.
:info:build performance hint: cython_lapack.pxd:245:24: No exception value declared for 'chla_transtype' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pyx:1563:5: Exception check on 'cladiv' will always require the GIL to be acquired. Declare 'cladiv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: cython_lapack.pxd:331:13: No exception value declared for 'clangb' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:333:13: No exception value declared for 'clange' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:335:13: No exception value declared for 'clangt' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:337:13: No exception value declared for 'clanhb' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:339:13: No exception value declared for 'clanhe' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:341:13: No exception value declared for 'clanhf' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:343:13: No exception value declared for 'clanhp' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:345:13: No exception value declared for 'clanhs' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:347:13: No exception value declared for 'clanht' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:349:13: No exception value declared for 'clansb' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:351:13: No exception value declared for 'clansp' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:353:13: No exception value declared for 'clansy' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:355:13: No exception value declared for 'clantb' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:357:13: No exception value declared for 'clantp' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:359:13: No exception value declared for 'clantr' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:901:16: No exception value declared for 'disnan' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:975:13: No exception value declared for 'dlamch' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:979:15: No exception value declared for 'dlaneg' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:981:13: No exception value declared for 'dlangb' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:983:13: No exception value declared for 'dlange' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:985:13: No exception value declared for 'dlangt' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:987:13: No exception value declared for 'dlanhs' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:989:13: No exception value declared for 'dlansb' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:991:13: No exception value declared for 'dlansf' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:993:13: No exception value declared for 'dlansp' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:995:13: No exception value declared for 'dlanst' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:997:13: No exception value declared for 'dlansy' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:999:13: No exception value declared for 'dlantb' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1001:13: No exception value declared for 'dlantp' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1003:13: No exception value declared for 'dlantr' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1013:13: No exception value declared for 'dlapy2' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1015:13: No exception value declared for 'dlapy3' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1511:13: No exception value declared for 'dzsum1' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1513:15: No exception value declared for 'icmax1' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1515:15: No exception value declared for 'ieeeck' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1517:15: No exception value declared for 'ilaclc' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1519:15: No exception value declared for 'ilaclr' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1521:16: No exception value declared for 'iladiag' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1523:15: No exception value declared for 'iladlc' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1525:15: No exception value declared for 'iladlr' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1527:16: No exception value declared for 'ilaprec' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1529:15: No exception value declared for 'ilaslc' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1531:15: No exception value declared for 'ilaslr' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1533:17: No exception value declared for 'ilatrans' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1535:16: No exception value declared for 'ilauplo' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1539:15: No exception value declared for 'ilazlc' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1541:15: No exception value declared for 'ilazlr' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1543:15: No exception value declared for 'izmax1' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1551:13: No exception value declared for 'scsum1' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1783:13: No exception value declared for 'slamch' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1787:13: No exception value declared for 'slangb' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1789:13: No exception value declared for 'slange' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1791:13: No exception value declared for 'slangt' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1793:13: No exception value declared for 'slanhs' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1795:13: No exception value declared for 'slansb' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1797:13: No exception value declared for 'slansf' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1799:13: No exception value declared for 'slansp' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1801:13: No exception value declared for 'slanst' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1803:13: No exception value declared for 'slansy' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1805:13: No exception value declared for 'slantb' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1807:13: No exception value declared for 'slantp' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1809:13: No exception value declared for 'slantr' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1819:13: No exception value declared for 'slapy2' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:1821:13: No exception value declared for 'slapy3' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pyx:2083:5: Exception check on 'zladiv' will always require the GIL to be acquired. Declare 'zladiv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: cython_lapack.pxd:2617:13: No exception value declared for 'zlangb' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:2619:13: No exception value declared for 'zlange' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:2621:13: No exception value declared for 'zlangt' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:2623:13: No exception value declared for 'zlanhb' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:2625:13: No exception value declared for 'zlanhe' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:2627:13: No exception value declared for 'zlanhf' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:2629:13: No exception value declared for 'zlanhp' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:2631:13: No exception value declared for 'zlanhs' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:2633:13: No exception value declared for 'zlanht' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:2635:13: No exception value declared for 'zlansb' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:2637:13: No exception value declared for 'zlansp' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:2639:13: No exception value declared for 'zlansy' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:2641:13: No exception value declared for 'zlantb' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:2643:13: No exception value declared for 'zlantp' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pxd:2645:13: No exception value declared for 'zlantr' in pxd file.
:info:build Users cimporting this function and calling it without the gil will always require an exception check.
:info:build Suggest adding an explicit exception value.
:info:build performance hint: cython_lapack.pyx:2210:5: Exception check on 'cbbcsd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cbbcsd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cbbcsd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2215:5: Exception check on 'cbdsqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cbdsqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cbdsqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2220:5: Exception check on 'cgbbrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgbbrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgbbrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2225:5: Exception check on 'cgbcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgbcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgbcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2230:5: Exception check on 'cgbequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgbequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgbequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2235:5: Exception check on 'cgbequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgbequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgbequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2240:5: Exception check on 'cgbrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgbrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgbrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2245:5: Exception check on 'cgbsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgbsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgbsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2250:5: Exception check on 'cgbsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgbsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgbsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2255:5: Exception check on 'cgbtf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgbtf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgbtf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2260:5: Exception check on 'cgbtrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgbtrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgbtrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2265:5: Exception check on 'cgbtrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgbtrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgbtrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2270:5: Exception check on 'cgebak' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgebak' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgebak' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2275:5: Exception check on 'cgebal' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgebal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgebal' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2280:5: Exception check on 'cgebd2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgebd2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgebd2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2285:5: Exception check on 'cgebrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgebrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgebrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2290:5: Exception check on 'cgecon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgecon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgecon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2295:5: Exception check on 'cgeequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgeequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgeequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2300:5: Exception check on 'cgeequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgeequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgeequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2305:5: Exception check on 'cgees' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgees' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgees' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2310:5: Exception check on 'cgeesx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgeesx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgeesx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2315:5: Exception check on 'cgeev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgeev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgeev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2320:5: Exception check on 'cgeevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgeevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgeevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2325:5: Exception check on 'cgehd2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgehd2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgehd2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2330:5: Exception check on 'cgehrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgehrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgehrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2335:5: Exception check on 'cgelq2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgelq2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgelq2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2340:5: Exception check on 'cgelqf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgelqf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgelqf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2345:5: Exception check on 'cgels' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgels' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgels' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2350:5: Exception check on 'cgelsd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgelsd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgelsd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2355:5: Exception check on 'cgelss' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgelss' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgelss' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2360:5: Exception check on 'cgelsy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgelsy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgelsy' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2365:5: Exception check on 'cgemqrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgemqrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgemqrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2370:5: Exception check on 'cgeql2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgeql2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgeql2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2375:5: Exception check on 'cgeqlf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgeqlf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgeqlf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2380:5: Exception check on 'cgeqp3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgeqp3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgeqp3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2385:5: Exception check on 'cgeqr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgeqr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgeqr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2390:5: Exception check on 'cgeqr2p' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgeqr2p' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgeqr2p' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2395:5: Exception check on 'cgeqrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgeqrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgeqrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2400:5: Exception check on 'cgeqrfp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgeqrfp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgeqrfp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2405:5: Exception check on 'cgeqrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgeqrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgeqrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2410:5: Exception check on 'cgeqrt2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgeqrt2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgeqrt2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2415:5: Exception check on 'cgeqrt3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgeqrt3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgeqrt3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2420:5: Exception check on 'cgerfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgerfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgerfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2425:5: Exception check on 'cgerq2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgerq2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgerq2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2430:5: Exception check on 'cgerqf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgerqf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgerqf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2435:5: Exception check on 'cgesc2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgesc2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgesc2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2440:5: Exception check on 'cgesdd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgesdd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgesdd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2445:5: Exception check on 'cgesv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgesv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgesv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2450:5: Exception check on 'cgesvd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgesvd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgesvd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2455:5: Exception check on 'cgesvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgesvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgesvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2460:5: Exception check on 'cgetc2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgetc2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgetc2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2465:5: Exception check on 'cgetf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgetf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgetf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2470:5: Exception check on 'cgetrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgetrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgetrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2475:5: Exception check on 'cgetri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgetri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgetri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2480:5: Exception check on 'cgetrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgetrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgetrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2485:5: Exception check on 'cggbak' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cggbak' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cggbak' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2490:5: Exception check on 'cggbal' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cggbal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cggbal' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2495:5: Exception check on 'cgges' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgges' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgges' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2500:5: Exception check on 'cggesx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cggesx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cggesx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2505:5: Exception check on 'cggev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cggev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cggev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2510:5: Exception check on 'cggevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cggevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cggevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2515:5: Exception check on 'cggglm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cggglm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cggglm' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2520:5: Exception check on 'cgghrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgghrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgghrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2525:5: Exception check on 'cgglse' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgglse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgglse' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2530:5: Exception check on 'cggqrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cggqrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cggqrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2535:5: Exception check on 'cggrqf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cggrqf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cggrqf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2540:5: Exception check on 'cgtcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgtcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgtcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2545:5: Exception check on 'cgtrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgtrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgtrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2550:5: Exception check on 'cgtsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgtsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgtsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2555:5: Exception check on 'cgtsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgtsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgtsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2560:5: Exception check on 'cgttrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgttrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgttrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2565:5: Exception check on 'cgttrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgttrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgttrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2570:5: Exception check on 'cgtts2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cgtts2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cgtts2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2575:5: Exception check on 'chbev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chbev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chbev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2580:5: Exception check on 'chbevd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chbevd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chbevd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2585:5: Exception check on 'chbevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chbevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chbevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2590:5: Exception check on 'chbgst' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chbgst' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chbgst' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2595:5: Exception check on 'chbgv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chbgv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chbgv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2600:5: Exception check on 'chbgvd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chbgvd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chbgvd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2605:5: Exception check on 'chbgvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chbgvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chbgvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2610:5: Exception check on 'chbtrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chbtrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chbtrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2615:5: Exception check on 'checon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'checon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'checon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2620:5: Exception check on 'cheequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cheequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cheequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2625:5: Exception check on 'cheev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cheev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cheev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2630:5: Exception check on 'cheevd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cheevd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cheevd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2635:5: Exception check on 'cheevr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cheevr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cheevr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2640:5: Exception check on 'cheevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cheevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cheevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2645:5: Exception check on 'chegs2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chegs2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chegs2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2650:5: Exception check on 'chegst' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chegst' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chegst' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2655:5: Exception check on 'chegv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chegv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chegv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2660:5: Exception check on 'chegvd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chegvd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chegvd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2665:5: Exception check on 'chegvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chegvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chegvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2670:5: Exception check on 'cherfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cherfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cherfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2675:5: Exception check on 'chesv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chesv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chesv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2680:5: Exception check on 'chesvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chesvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chesvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2685:5: Exception check on 'cheswapr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cheswapr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cheswapr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2690:5: Exception check on 'chetd2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chetd2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chetd2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2695:5: Exception check on 'chetf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chetf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chetf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2700:5: Exception check on 'chetrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chetrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chetrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2705:5: Exception check on 'chetrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chetrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chetrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2710:5: Exception check on 'chetri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chetri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chetri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2715:5: Exception check on 'chetri2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chetri2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chetri2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2720:5: Exception check on 'chetri2x' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chetri2x' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chetri2x' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2725:5: Exception check on 'chetrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chetrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chetrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2730:5: Exception check on 'chetrs2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chetrs2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chetrs2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2735:5: Exception check on 'chfrk' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chfrk' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chfrk' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2740:5: Exception check on 'chgeqz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chgeqz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chgeqz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2745:5: Exception check on 'chpcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chpcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chpcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2750:5: Exception check on 'chpev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chpev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chpev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2755:5: Exception check on 'chpevd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chpevd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chpevd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2760:5: Exception check on 'chpevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chpevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chpevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2765:5: Exception check on 'chpgst' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chpgst' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chpgst' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2770:5: Exception check on 'chpgv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chpgv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chpgv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2775:5: Exception check on 'chpgvd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chpgvd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chpgvd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2780:5: Exception check on 'chpgvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chpgvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chpgvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2785:5: Exception check on 'chprfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chprfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chprfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2790:5: Exception check on 'chpsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chpsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chpsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2795:5: Exception check on 'chpsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chpsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chpsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2800:5: Exception check on 'chptrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chptrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chptrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2805:5: Exception check on 'chptrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chptrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chptrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2810:5: Exception check on 'chptri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chptri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chptri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2815:5: Exception check on 'chptrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chptrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chptrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2820:5: Exception check on 'chsein' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chsein' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chsein' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2825:5: Exception check on 'chseqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'chseqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'chseqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2830:5: Exception check on 'clabrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clabrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clabrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2835:5: Exception check on 'clacgv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clacgv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clacgv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2840:5: Exception check on 'clacn2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clacn2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clacn2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2845:5: Exception check on 'clacon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clacon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clacon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2850:5: Exception check on 'clacp2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clacp2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clacp2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2855:5: Exception check on 'clacpy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clacpy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clacpy' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2860:5: Exception check on 'clacrm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clacrm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clacrm' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2865:5: Exception check on 'clacrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clacrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clacrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2870:5: Exception check on 'claed0' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claed0' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claed0' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2875:5: Exception check on 'claed7' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claed7' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claed7' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2880:5: Exception check on 'claed8' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claed8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claed8' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2885:5: Exception check on 'claein' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claein' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claein' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2890:5: Exception check on 'claesy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claesy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claesy' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2895:5: Exception check on 'claev2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claev2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claev2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2900:5: Exception check on 'clag2z' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clag2z' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clag2z' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2905:5: Exception check on 'clags2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clags2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clags2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2910:5: Exception check on 'clagtm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clagtm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clagtm' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2915:5: Exception check on 'clahef' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clahef' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clahef' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2920:5: Exception check on 'clahqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clahqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clahqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2925:5: Exception check on 'clahr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clahr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clahr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2930:5: Exception check on 'claic1' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claic1' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claic1' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2935:5: Exception check on 'clals0' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clals0' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clals0' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2940:5: Exception check on 'clalsa' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clalsa' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clalsa' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2945:5: Exception check on 'clalsd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clalsd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clalsd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2950:5: Exception check on 'clapll' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clapll' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clapll' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2955:5: Exception check on 'clapmr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clapmr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clapmr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2960:5: Exception check on 'clapmt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clapmt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clapmt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2965:5: Exception check on 'claqgb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claqgb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claqgb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2970:5: Exception check on 'claqge' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claqge' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claqge' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2975:5: Exception check on 'claqhb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claqhb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claqhb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2980:5: Exception check on 'claqhe' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claqhe' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claqhe' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2985:5: Exception check on 'claqhp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claqhp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claqhp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2990:5: Exception check on 'claqp2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claqp2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claqp2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2995:5: Exception check on 'claqps' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claqps' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claqps' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3000:5: Exception check on 'claqr0' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claqr0' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claqr0' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3005:5: Exception check on 'claqr1' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claqr1' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claqr1' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3010:5: Exception check on 'claqr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claqr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claqr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3015:5: Exception check on 'claqr3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claqr3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claqr3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3020:5: Exception check on 'claqr4' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claqr4' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claqr4' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3025:5: Exception check on 'claqr5' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claqr5' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claqr5' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3030:5: Exception check on 'claqsb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claqsb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claqsb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3035:5: Exception check on 'claqsp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claqsp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claqsp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3040:5: Exception check on 'claqsy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claqsy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claqsy' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3045:5: Exception check on 'clar1v' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clar1v' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clar1v' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3050:5: Exception check on 'clar2v' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clar2v' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clar2v' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3055:5: Exception check on 'clarcm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clarcm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clarcm' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3060:5: Exception check on 'clarf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clarf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clarf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3065:5: Exception check on 'clarfb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clarfb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clarfb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3070:5: Exception check on 'clarfg' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clarfg' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clarfg' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3075:5: Exception check on 'clarfgp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clarfgp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clarfgp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3080:5: Exception check on 'clarft' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clarft' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clarft' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3085:5: Exception check on 'clarfx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clarfx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clarfx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3090:5: Exception check on 'clargv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clargv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clargv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3095:5: Exception check on 'clarnv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clarnv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clarnv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3100:5: Exception check on 'clarrv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clarrv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clarrv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3105:5: Exception check on 'clartg' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clartg' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clartg' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3110:5: Exception check on 'clartv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clartv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clartv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3115:5: Exception check on 'clarz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clarz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clarz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3120:5: Exception check on 'clarzb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clarzb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clarzb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3125:5: Exception check on 'clarzt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clarzt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clarzt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3130:5: Exception check on 'clascl' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clascl' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clascl' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3135:5: Exception check on 'claset' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claset' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claset' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3140:5: Exception check on 'clasr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clasr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clasr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3145:5: Exception check on 'classq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'classq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'classq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3150:5: Exception check on 'claswp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'claswp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'claswp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3155:5: Exception check on 'clasyf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clasyf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clasyf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3160:5: Exception check on 'clatbs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clatbs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clatbs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3165:5: Exception check on 'clatdf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clatdf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clatdf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3170:5: Exception check on 'clatps' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clatps' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clatps' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3175:5: Exception check on 'clatrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clatrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clatrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3180:5: Exception check on 'clatrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clatrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clatrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3185:5: Exception check on 'clatrz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clatrz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clatrz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3190:5: Exception check on 'clauu2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clauu2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clauu2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3195:5: Exception check on 'clauum' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'clauum' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'clauum' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3200:5: Exception check on 'cpbcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpbcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpbcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3205:5: Exception check on 'cpbequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpbequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpbequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3210:5: Exception check on 'cpbrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpbrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpbrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3215:5: Exception check on 'cpbstf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpbstf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpbstf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3220:5: Exception check on 'cpbsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpbsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpbsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3225:5: Exception check on 'cpbsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpbsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpbsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3230:5: Exception check on 'cpbtf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpbtf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpbtf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3235:5: Exception check on 'cpbtrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpbtrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpbtrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3240:5: Exception check on 'cpbtrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpbtrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpbtrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3245:5: Exception check on 'cpftrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpftrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpftrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3250:5: Exception check on 'cpftri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpftri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpftri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3255:5: Exception check on 'cpftrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpftrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpftrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3260:5: Exception check on 'cpocon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpocon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpocon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3265:5: Exception check on 'cpoequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpoequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpoequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3270:5: Exception check on 'cpoequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpoequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpoequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3275:5: Exception check on 'cporfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cporfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cporfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3280:5: Exception check on 'cposv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cposv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cposv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3285:5: Exception check on 'cposvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cposvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cposvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3290:5: Exception check on 'cpotf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpotf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpotf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3295:5: Exception check on 'cpotrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpotrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpotrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3300:5: Exception check on 'cpotri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpotri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpotri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3305:5: Exception check on 'cpotrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpotrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpotrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3310:5: Exception check on 'cppcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cppcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cppcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3315:5: Exception check on 'cppequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cppequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cppequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3320:5: Exception check on 'cpprfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpprfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpprfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3325:5: Exception check on 'cppsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cppsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cppsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3330:5: Exception check on 'cppsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cppsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cppsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3335:5: Exception check on 'cpptrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpptrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpptrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3340:5: Exception check on 'cpptri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpptri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpptri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3345:5: Exception check on 'cpptrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpptrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpptrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3350:5: Exception check on 'cpstf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpstf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpstf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3355:5: Exception check on 'cpstrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpstrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpstrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3360:5: Exception check on 'cptcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cptcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cptcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3365:5: Exception check on 'cpteqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpteqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpteqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3370:5: Exception check on 'cptrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cptrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cptrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3375:5: Exception check on 'cptsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cptsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cptsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3380:5: Exception check on 'cptsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cptsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cptsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3385:5: Exception check on 'cpttrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpttrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpttrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3390:5: Exception check on 'cpttrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cpttrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cpttrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3395:5: Exception check on 'cptts2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cptts2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cptts2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3400:5: Exception check on 'crot' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'crot' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'crot' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3405:5: Exception check on 'cspcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cspcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cspcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3410:5: Exception check on 'cspmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cspmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cspmv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3415:5: Exception check on 'cspr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cspr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cspr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3420:5: Exception check on 'csprfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csprfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csprfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3425:5: Exception check on 'cspsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cspsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cspsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3430:5: Exception check on 'cspsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cspsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cspsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3435:5: Exception check on 'csptrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csptrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csptrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3440:5: Exception check on 'csptri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csptri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csptri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3445:5: Exception check on 'csptrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csptrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csptrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3450:5: Exception check on 'csrscl' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csrscl' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csrscl' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3455:5: Exception check on 'cstedc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cstedc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cstedc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3460:5: Exception check on 'cstegr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cstegr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cstegr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3465:5: Exception check on 'cstein' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cstein' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cstein' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3470:5: Exception check on 'cstemr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cstemr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cstemr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3475:5: Exception check on 'csteqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csteqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csteqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3480:5: Exception check on 'csycon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csycon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csycon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3485:5: Exception check on 'csyconv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csyconv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csyconv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3490:5: Exception check on 'csyequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csyequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csyequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3495:5: Exception check on 'csymv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csymv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csymv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3500:5: Exception check on 'csyr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csyr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csyr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3505:5: Exception check on 'csyrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csyrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csyrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3510:5: Exception check on 'csysv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csysv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csysv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3515:5: Exception check on 'csysvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csysvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csysvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3520:5: Exception check on 'csyswapr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csyswapr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csyswapr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3525:5: Exception check on 'csytf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csytf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csytf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3530:5: Exception check on 'csytrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csytrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csytrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3535:5: Exception check on 'csytri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csytri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csytri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3540:5: Exception check on 'csytri2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csytri2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csytri2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3545:5: Exception check on 'csytri2x' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csytri2x' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csytri2x' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3550:5: Exception check on 'csytrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csytrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csytrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3555:5: Exception check on 'csytrs2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'csytrs2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'csytrs2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3560:5: Exception check on 'ctbcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctbcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctbcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3565:5: Exception check on 'ctbrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctbrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctbrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3570:5: Exception check on 'ctbtrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctbtrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctbtrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3575:5: Exception check on 'ctfsm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctfsm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctfsm' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3580:5: Exception check on 'ctftri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctftri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctftri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3585:5: Exception check on 'ctfttp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctfttp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctfttp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3590:5: Exception check on 'ctfttr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctfttr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctfttr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3595:5: Exception check on 'ctgevc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctgevc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctgevc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3600:5: Exception check on 'ctgex2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctgex2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctgex2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3605:5: Exception check on 'ctgexc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctgexc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctgexc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3610:5: Exception check on 'ctgsen' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctgsen' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctgsen' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3615:5: Exception check on 'ctgsja' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctgsja' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctgsja' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3620:5: Exception check on 'ctgsna' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctgsna' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctgsna' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3625:5: Exception check on 'ctgsy2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctgsy2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctgsy2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3630:5: Exception check on 'ctgsyl' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctgsyl' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctgsyl' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3635:5: Exception check on 'ctpcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctpcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctpcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3640:5: Exception check on 'ctpmqrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctpmqrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctpmqrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3645:5: Exception check on 'ctpqrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctpqrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctpqrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3650:5: Exception check on 'ctpqrt2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctpqrt2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctpqrt2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3655:5: Exception check on 'ctprfb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctprfb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctprfb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3660:5: Exception check on 'ctprfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctprfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctprfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3665:5: Exception check on 'ctptri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctptri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctptri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3670:5: Exception check on 'ctptrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctptrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctptrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3675:5: Exception check on 'ctpttf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctpttf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctpttf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3680:5: Exception check on 'ctpttr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctpttr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctpttr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3685:5: Exception check on 'ctrcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctrcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctrcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3690:5: Exception check on 'ctrevc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctrevc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctrevc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3695:5: Exception check on 'ctrexc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctrexc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctrexc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3700:5: Exception check on 'ctrrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctrrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctrrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3705:5: Exception check on 'ctrsen' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctrsen' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctrsen' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3710:5: Exception check on 'ctrsna' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctrsna' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctrsna' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3715:5: Exception check on 'ctrsyl' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctrsyl' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctrsyl' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3720:5: Exception check on 'ctrti2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctrti2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctrti2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3725:5: Exception check on 'ctrtri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctrtri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctrtri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3730:5: Exception check on 'ctrtrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctrtrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctrtrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3735:5: Exception check on 'ctrttf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctrttf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctrttf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3740:5: Exception check on 'ctrttp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctrttp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctrttp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3745:5: Exception check on 'ctzrzf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ctzrzf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ctzrzf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3750:5: Exception check on 'cunbdb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cunbdb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cunbdb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3755:5: Exception check on 'cuncsd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cuncsd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cuncsd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3760:5: Exception check on 'cung2l' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cung2l' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cung2l' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3765:5: Exception check on 'cung2r' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cung2r' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cung2r' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3770:5: Exception check on 'cungbr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cungbr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cungbr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3775:5: Exception check on 'cunghr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cunghr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cunghr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3780:5: Exception check on 'cungl2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cungl2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cungl2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3785:5: Exception check on 'cunglq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cunglq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cunglq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3790:5: Exception check on 'cungql' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cungql' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cungql' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3795:5: Exception check on 'cungqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cungqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cungqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3800:5: Exception check on 'cungr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cungr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cungr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3805:5: Exception check on 'cungrq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cungrq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cungrq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3810:5: Exception check on 'cungtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cungtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cungtr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3815:5: Exception check on 'cunm2l' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cunm2l' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cunm2l' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3820:5: Exception check on 'cunm2r' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cunm2r' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cunm2r' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3825:5: Exception check on 'cunmbr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cunmbr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cunmbr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3830:5: Exception check on 'cunmhr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cunmhr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cunmhr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3835:5: Exception check on 'cunml2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cunml2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cunml2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3840:5: Exception check on 'cunmlq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cunmlq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cunmlq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3845:5: Exception check on 'cunmql' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cunmql' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cunmql' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3850:5: Exception check on 'cunmqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cunmqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cunmqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3855:5: Exception check on 'cunmr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cunmr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cunmr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3860:5: Exception check on 'cunmr3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cunmr3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cunmr3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3865:5: Exception check on 'cunmrq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cunmrq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cunmrq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3870:5: Exception check on 'cunmrz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cunmrz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cunmrz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3875:5: Exception check on 'cunmtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cunmtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cunmtr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3880:5: Exception check on 'cupgtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cupgtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cupgtr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3885:5: Exception check on 'cupmtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'cupmtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'cupmtr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3890:5: Exception check on 'dbbcsd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dbbcsd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dbbcsd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3895:5: Exception check on 'dbdsdc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dbdsdc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dbdsdc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3900:5: Exception check on 'dbdsqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dbdsqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dbdsqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3905:5: Exception check on 'ddisna' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ddisna' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ddisna' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3910:5: Exception check on 'dgbbrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgbbrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgbbrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3915:5: Exception check on 'dgbcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgbcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgbcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3920:5: Exception check on 'dgbequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgbequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgbequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3925:5: Exception check on 'dgbequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgbequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgbequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3930:5: Exception check on 'dgbrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgbrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgbrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3935:5: Exception check on 'dgbsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgbsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgbsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3940:5: Exception check on 'dgbsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgbsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgbsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3945:5: Exception check on 'dgbtf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgbtf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgbtf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3950:5: Exception check on 'dgbtrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgbtrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgbtrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3955:5: Exception check on 'dgbtrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgbtrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgbtrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3960:5: Exception check on 'dgebak' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgebak' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgebak' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3965:5: Exception check on 'dgebal' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgebal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgebal' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3970:5: Exception check on 'dgebd2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgebd2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgebd2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3975:5: Exception check on 'dgebrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgebrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgebrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3980:5: Exception check on 'dgecon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgecon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgecon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3985:5: Exception check on 'dgeequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgeequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgeequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3990:5: Exception check on 'dgeequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgeequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgeequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:3995:5: Exception check on 'dgees' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgees' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgees' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4000:5: Exception check on 'dgeesx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgeesx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgeesx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4005:5: Exception check on 'dgeev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgeev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgeev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4010:5: Exception check on 'dgeevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgeevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgeevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4015:5: Exception check on 'dgehd2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgehd2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgehd2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4020:5: Exception check on 'dgehrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgehrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgehrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4025:5: Exception check on 'dgejsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgejsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgejsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4030:5: Exception check on 'dgelq2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgelq2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgelq2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4035:5: Exception check on 'dgelqf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgelqf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgelqf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4040:5: Exception check on 'dgels' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgels' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgels' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4045:5: Exception check on 'dgelsd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgelsd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgelsd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4050:5: Exception check on 'dgelss' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgelss' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgelss' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4055:5: Exception check on 'dgelsy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgelsy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgelsy' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4060:5: Exception check on 'dgemqrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgemqrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgemqrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4065:5: Exception check on 'dgeql2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgeql2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgeql2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4070:5: Exception check on 'dgeqlf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgeqlf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgeqlf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4075:5: Exception check on 'dgeqp3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgeqp3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgeqp3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4080:5: Exception check on 'dgeqr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgeqr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgeqr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4085:5: Exception check on 'dgeqr2p' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgeqr2p' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgeqr2p' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4090:5: Exception check on 'dgeqrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgeqrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgeqrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4095:5: Exception check on 'dgeqrfp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgeqrfp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgeqrfp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4100:5: Exception check on 'dgeqrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgeqrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgeqrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4105:5: Exception check on 'dgeqrt2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgeqrt2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgeqrt2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4110:5: Exception check on 'dgeqrt3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgeqrt3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgeqrt3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4115:5: Exception check on 'dgerfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgerfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgerfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4120:5: Exception check on 'dgerq2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgerq2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgerq2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4125:5: Exception check on 'dgerqf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgerqf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgerqf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4130:5: Exception check on 'dgesc2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgesc2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgesc2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4135:5: Exception check on 'dgesdd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgesdd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgesdd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4140:5: Exception check on 'dgesv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgesv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgesv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4145:5: Exception check on 'dgesvd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgesvd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgesvd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4150:5: Exception check on 'dgesvj' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgesvj' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgesvj' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4155:5: Exception check on 'dgesvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgesvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgesvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4160:5: Exception check on 'dgetc2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgetc2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgetc2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4165:5: Exception check on 'dgetf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgetf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgetf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4170:5: Exception check on 'dgetrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgetrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgetrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4175:5: Exception check on 'dgetri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgetri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgetri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4180:5: Exception check on 'dgetrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgetrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgetrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4185:5: Exception check on 'dggbak' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dggbak' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dggbak' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4190:5: Exception check on 'dggbal' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dggbal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dggbal' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4195:5: Exception check on 'dgges' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgges' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgges' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4200:5: Exception check on 'dggesx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dggesx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dggesx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4205:5: Exception check on 'dggev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dggev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dggev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4210:5: Exception check on 'dggevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dggevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dggevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4215:5: Exception check on 'dggglm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dggglm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dggglm' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4220:5: Exception check on 'dgghrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgghrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgghrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4225:5: Exception check on 'dgglse' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgglse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgglse' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4230:5: Exception check on 'dggqrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dggqrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dggqrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4235:5: Exception check on 'dggrqf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dggrqf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dggrqf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4240:5: Exception check on 'dgsvj0' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgsvj0' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgsvj0' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4245:5: Exception check on 'dgsvj1' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgsvj1' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgsvj1' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4250:5: Exception check on 'dgtcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgtcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgtcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4255:5: Exception check on 'dgtrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgtrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgtrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4260:5: Exception check on 'dgtsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgtsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgtsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4265:5: Exception check on 'dgtsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgtsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgtsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4270:5: Exception check on 'dgttrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgttrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgttrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4275:5: Exception check on 'dgttrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgttrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgttrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4280:5: Exception check on 'dgtts2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dgtts2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dgtts2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4285:5: Exception check on 'dhgeqz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dhgeqz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dhgeqz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4290:5: Exception check on 'dhsein' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dhsein' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dhsein' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4295:5: Exception check on 'dhseqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dhseqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dhseqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4300:5: Exception check on 'dlabad' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlabad' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlabad' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4305:5: Exception check on 'dlabrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlabrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlabrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4310:5: Exception check on 'dlacn2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlacn2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlacn2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4315:5: Exception check on 'dlacon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlacon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlacon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4320:5: Exception check on 'dlacpy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlacpy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlacpy' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4325:5: Exception check on 'dladiv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dladiv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dladiv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4330:5: Exception check on 'dlae2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlae2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlae2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4335:5: Exception check on 'dlaebz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaebz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaebz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4340:5: Exception check on 'dlaed0' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaed0' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaed0' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4345:5: Exception check on 'dlaed1' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaed1' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaed1' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4350:5: Exception check on 'dlaed2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaed2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaed2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4355:5: Exception check on 'dlaed3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaed3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaed3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4360:5: Exception check on 'dlaed4' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaed4' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaed4' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4365:5: Exception check on 'dlaed5' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaed5' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaed5' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4370:5: Exception check on 'dlaed6' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaed6' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaed6' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4375:5: Exception check on 'dlaed7' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaed7' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaed7' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4380:5: Exception check on 'dlaed8' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaed8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaed8' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4385:5: Exception check on 'dlaed9' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaed9' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaed9' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4390:5: Exception check on 'dlaeda' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaeda' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaeda' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4395:5: Exception check on 'dlaein' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaein' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaein' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4400:5: Exception check on 'dlaev2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaev2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaev2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4405:5: Exception check on 'dlaexc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaexc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaexc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4410:5: Exception check on 'dlag2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlag2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlag2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4415:5: Exception check on 'dlag2s' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlag2s' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlag2s' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4420:5: Exception check on 'dlags2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlags2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlags2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4425:5: Exception check on 'dlagtf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlagtf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlagtf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4430:5: Exception check on 'dlagtm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlagtm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlagtm' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4435:5: Exception check on 'dlagts' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlagts' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlagts' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4440:5: Exception check on 'dlagv2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlagv2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlagv2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4445:5: Exception check on 'dlahqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlahqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlahqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4450:5: Exception check on 'dlahr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlahr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlahr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4455:5: Exception check on 'dlaic1' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaic1' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaic1' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4460:5: Exception check on 'dlaln2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaln2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaln2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4465:5: Exception check on 'dlals0' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlals0' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlals0' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4470:5: Exception check on 'dlalsa' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlalsa' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlalsa' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4475:5: Exception check on 'dlalsd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlalsd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlalsd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4480:5: Exception check on 'dlamrg' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlamrg' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlamrg' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4485:5: Exception check on 'dlanv2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlanv2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlanv2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4490:5: Exception check on 'dlapll' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlapll' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlapll' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4495:5: Exception check on 'dlapmr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlapmr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlapmr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4500:5: Exception check on 'dlapmt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlapmt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlapmt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4505:5: Exception check on 'dlaqgb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaqgb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaqgb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4510:5: Exception check on 'dlaqge' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaqge' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaqge' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4515:5: Exception check on 'dlaqp2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaqp2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaqp2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4520:5: Exception check on 'dlaqps' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaqps' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaqps' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4525:5: Exception check on 'dlaqr0' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaqr0' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaqr0' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4530:5: Exception check on 'dlaqr1' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaqr1' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaqr1' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4535:5: Exception check on 'dlaqr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaqr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaqr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4540:5: Exception check on 'dlaqr3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaqr3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaqr3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4545:5: Exception check on 'dlaqr4' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaqr4' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaqr4' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4550:5: Exception check on 'dlaqr5' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaqr5' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaqr5' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4555:5: Exception check on 'dlaqsb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaqsb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaqsb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4560:5: Exception check on 'dlaqsp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaqsp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaqsp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4565:5: Exception check on 'dlaqsy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaqsy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaqsy' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4570:5: Exception check on 'dlaqtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaqtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaqtr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4575:5: Exception check on 'dlar1v' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlar1v' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlar1v' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4580:5: Exception check on 'dlar2v' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlar2v' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlar2v' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4585:5: Exception check on 'dlarf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4590:5: Exception check on 'dlarfb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarfb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarfb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4595:5: Exception check on 'dlarfg' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarfg' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarfg' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4600:5: Exception check on 'dlarfgp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarfgp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarfgp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4605:5: Exception check on 'dlarft' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarft' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarft' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4610:5: Exception check on 'dlarfx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarfx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarfx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4615:5: Exception check on 'dlargv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlargv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlargv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4620:5: Exception check on 'dlarnv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarnv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarnv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4625:5: Exception check on 'dlarra' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarra' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarra' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4630:5: Exception check on 'dlarrb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarrb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarrb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4635:5: Exception check on 'dlarrc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarrc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarrc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4640:5: Exception check on 'dlarrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4645:5: Exception check on 'dlarre' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarre' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarre' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4650:5: Exception check on 'dlarrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4655:5: Exception check on 'dlarrj' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarrj' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarrj' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4660:5: Exception check on 'dlarrk' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarrk' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarrk' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4665:5: Exception check on 'dlarrr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarrr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarrr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4670:5: Exception check on 'dlarrv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarrv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarrv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4675:5: Exception check on 'dlartg' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlartg' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlartg' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4680:5: Exception check on 'dlartgp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlartgp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlartgp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4685:5: Exception check on 'dlartgs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlartgs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlartgs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4690:5: Exception check on 'dlartv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlartv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlartv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4695:5: Exception check on 'dlaruv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaruv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaruv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4700:5: Exception check on 'dlarz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4705:5: Exception check on 'dlarzb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarzb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarzb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4710:5: Exception check on 'dlarzt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlarzt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlarzt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4715:5: Exception check on 'dlas2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlas2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlas2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4720:5: Exception check on 'dlascl' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlascl' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlascl' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4725:5: Exception check on 'dlasd0' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasd0' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasd0' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4730:5: Exception check on 'dlasd1' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasd1' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasd1' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4735:5: Exception check on 'dlasd2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasd2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasd2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4740:5: Exception check on 'dlasd3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasd3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasd3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4745:5: Exception check on 'dlasd4' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasd4' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasd4' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4750:5: Exception check on 'dlasd5' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasd5' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasd5' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4755:5: Exception check on 'dlasd6' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasd6' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasd6' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4760:5: Exception check on 'dlasd7' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasd7' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasd7' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4765:5: Exception check on 'dlasd8' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasd8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasd8' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4770:5: Exception check on 'dlasda' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasda' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasda' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4775:5: Exception check on 'dlasdq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasdq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasdq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4780:5: Exception check on 'dlasdt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasdt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasdt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4785:5: Exception check on 'dlaset' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaset' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaset' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4790:5: Exception check on 'dlasq1' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasq1' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasq1' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4795:5: Exception check on 'dlasq2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasq2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasq2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4800:5: Exception check on 'dlasq3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasq3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasq3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4805:5: Exception check on 'dlasq4' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasq4' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasq4' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4810:5: Exception check on 'dlasq6' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasq6' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasq6' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4815:5: Exception check on 'dlasr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4820:5: Exception check on 'dlasrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4825:5: Exception check on 'dlassq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlassq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlassq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4830:5: Exception check on 'dlasv2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasv2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasv2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4835:5: Exception check on 'dlaswp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlaswp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlaswp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4840:5: Exception check on 'dlasy2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasy2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasy2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4845:5: Exception check on 'dlasyf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlasyf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlasyf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4850:5: Exception check on 'dlat2s' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlat2s' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlat2s' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4855:5: Exception check on 'dlatbs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlatbs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlatbs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4860:5: Exception check on 'dlatdf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlatdf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlatdf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4865:5: Exception check on 'dlatps' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlatps' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlatps' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4870:5: Exception check on 'dlatrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlatrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlatrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4875:5: Exception check on 'dlatrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlatrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlatrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4880:5: Exception check on 'dlatrz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlatrz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlatrz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4885:5: Exception check on 'dlauu2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlauu2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlauu2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4890:5: Exception check on 'dlauum' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dlauum' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dlauum' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4895:5: Exception check on 'dopgtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dopgtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dopgtr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4900:5: Exception check on 'dopmtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dopmtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dopmtr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4905:5: Exception check on 'dorbdb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dorbdb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dorbdb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4910:5: Exception check on 'dorcsd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dorcsd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dorcsd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4915:5: Exception check on 'dorg2l' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dorg2l' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dorg2l' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4920:5: Exception check on 'dorg2r' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dorg2r' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dorg2r' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4925:5: Exception check on 'dorgbr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dorgbr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dorgbr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4930:5: Exception check on 'dorghr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dorghr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dorghr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4935:5: Exception check on 'dorgl2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dorgl2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dorgl2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4940:5: Exception check on 'dorglq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dorglq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dorglq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4945:5: Exception check on 'dorgql' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dorgql' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dorgql' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4950:5: Exception check on 'dorgqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dorgqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dorgqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4955:5: Exception check on 'dorgr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dorgr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dorgr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4960:5: Exception check on 'dorgrq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dorgrq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dorgrq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4965:5: Exception check on 'dorgtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dorgtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dorgtr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4970:5: Exception check on 'dorm2l' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dorm2l' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dorm2l' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4975:5: Exception check on 'dorm2r' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dorm2r' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dorm2r' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4980:5: Exception check on 'dormbr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dormbr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dormbr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4985:5: Exception check on 'dormhr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dormhr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dormhr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4990:5: Exception check on 'dorml2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dorml2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dorml2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:4995:5: Exception check on 'dormlq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dormlq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dormlq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5000:5: Exception check on 'dormql' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dormql' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dormql' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5005:5: Exception check on 'dormqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dormqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dormqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5010:5: Exception check on 'dormr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dormr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dormr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5015:5: Exception check on 'dormr3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dormr3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dormr3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5020:5: Exception check on 'dormrq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dormrq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dormrq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5025:5: Exception check on 'dormrz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dormrz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dormrz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5030:5: Exception check on 'dormtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dormtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dormtr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5035:5: Exception check on 'dpbcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpbcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpbcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5040:5: Exception check on 'dpbequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpbequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpbequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5045:5: Exception check on 'dpbrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpbrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpbrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5050:5: Exception check on 'dpbstf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpbstf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpbstf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5055:5: Exception check on 'dpbsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpbsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpbsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5060:5: Exception check on 'dpbsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpbsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpbsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5065:5: Exception check on 'dpbtf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpbtf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpbtf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5070:5: Exception check on 'dpbtrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpbtrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpbtrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5075:5: Exception check on 'dpbtrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpbtrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpbtrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5080:5: Exception check on 'dpftrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpftrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpftrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5085:5: Exception check on 'dpftri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpftri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpftri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5090:5: Exception check on 'dpftrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpftrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpftrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5095:5: Exception check on 'dpocon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpocon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpocon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5100:5: Exception check on 'dpoequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpoequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpoequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5105:5: Exception check on 'dpoequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpoequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpoequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5110:5: Exception check on 'dporfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dporfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dporfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5115:5: Exception check on 'dposv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dposv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dposv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5120:5: Exception check on 'dposvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dposvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dposvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5125:5: Exception check on 'dpotf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpotf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpotf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5130:5: Exception check on 'dpotrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpotrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpotrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5135:5: Exception check on 'dpotri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpotri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpotri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5140:5: Exception check on 'dpotrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpotrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpotrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5145:5: Exception check on 'dppcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dppcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dppcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5150:5: Exception check on 'dppequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dppequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dppequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5155:5: Exception check on 'dpprfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpprfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpprfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5160:5: Exception check on 'dppsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dppsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dppsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5165:5: Exception check on 'dppsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dppsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dppsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5170:5: Exception check on 'dpptrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpptrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpptrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5175:5: Exception check on 'dpptri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpptri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpptri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5180:5: Exception check on 'dpptrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpptrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpptrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5185:5: Exception check on 'dpstf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpstf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpstf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5190:5: Exception check on 'dpstrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpstrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpstrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5195:5: Exception check on 'dptcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dptcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dptcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5200:5: Exception check on 'dpteqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpteqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpteqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5205:5: Exception check on 'dptrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dptrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dptrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5210:5: Exception check on 'dptsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dptsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dptsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5215:5: Exception check on 'dptsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dptsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dptsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5220:5: Exception check on 'dpttrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpttrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpttrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5225:5: Exception check on 'dpttrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dpttrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dpttrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5230:5: Exception check on 'dptts2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dptts2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dptts2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5235:5: Exception check on 'drscl' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'drscl' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'drscl' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5240:5: Exception check on 'dsbev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsbev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsbev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5245:5: Exception check on 'dsbevd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsbevd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsbevd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5250:5: Exception check on 'dsbevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsbevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsbevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5255:5: Exception check on 'dsbgst' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsbgst' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsbgst' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5260:5: Exception check on 'dsbgv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsbgv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsbgv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5265:5: Exception check on 'dsbgvd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsbgvd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsbgvd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5270:5: Exception check on 'dsbgvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsbgvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsbgvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5275:5: Exception check on 'dsbtrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsbtrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsbtrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5280:5: Exception check on 'dsfrk' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsfrk' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsfrk' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5285:5: Exception check on 'dsgesv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsgesv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsgesv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5290:5: Exception check on 'dspcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dspcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dspcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5295:5: Exception check on 'dspev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dspev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dspev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5300:5: Exception check on 'dspevd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dspevd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dspevd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5305:5: Exception check on 'dspevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dspevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dspevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5310:5: Exception check on 'dspgst' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dspgst' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dspgst' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5315:5: Exception check on 'dspgv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dspgv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dspgv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5320:5: Exception check on 'dspgvd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dspgvd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dspgvd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5325:5: Exception check on 'dspgvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dspgvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dspgvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5330:5: Exception check on 'dsposv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsposv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsposv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5335:5: Exception check on 'dsprfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsprfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsprfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5340:5: Exception check on 'dspsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dspsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dspsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5345:5: Exception check on 'dspsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dspsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dspsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5350:5: Exception check on 'dsptrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsptrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsptrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5355:5: Exception check on 'dsptrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsptrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsptrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5360:5: Exception check on 'dsptri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsptri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsptri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5365:5: Exception check on 'dsptrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsptrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsptrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5370:5: Exception check on 'dstebz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dstebz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dstebz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5375:5: Exception check on 'dstedc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dstedc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dstedc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5380:5: Exception check on 'dstegr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dstegr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dstegr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5385:5: Exception check on 'dstein' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dstein' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dstein' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5390:5: Exception check on 'dstemr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dstemr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dstemr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5395:5: Exception check on 'dsteqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsteqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsteqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5400:5: Exception check on 'dsterf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsterf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsterf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5405:5: Exception check on 'dstev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dstev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dstev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5410:5: Exception check on 'dstevd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dstevd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dstevd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5415:5: Exception check on 'dstevr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dstevr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dstevr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5420:5: Exception check on 'dstevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dstevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dstevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5425:5: Exception check on 'dsycon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsycon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsycon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5430:5: Exception check on 'dsyconv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsyconv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsyconv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5435:5: Exception check on 'dsyequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsyequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsyequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5440:5: Exception check on 'dsyev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsyev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsyev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5445:5: Exception check on 'dsyevd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsyevd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsyevd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5450:5: Exception check on 'dsyevr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsyevr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsyevr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5455:5: Exception check on 'dsyevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsyevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsyevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5460:5: Exception check on 'dsygs2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsygs2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsygs2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5465:5: Exception check on 'dsygst' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsygst' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsygst' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5470:5: Exception check on 'dsygv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsygv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsygv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5475:5: Exception check on 'dsygvd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsygvd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsygvd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5480:5: Exception check on 'dsygvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsygvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsygvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5485:5: Exception check on 'dsyrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsyrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsyrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5490:5: Exception check on 'dsysv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsysv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsysv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5495:5: Exception check on 'dsysvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsysvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsysvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5500:5: Exception check on 'dsyswapr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsyswapr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsyswapr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5505:5: Exception check on 'dsytd2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsytd2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsytd2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5510:5: Exception check on 'dsytf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsytf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsytf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5515:5: Exception check on 'dsytrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsytrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsytrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5520:5: Exception check on 'dsytrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsytrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsytrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5525:5: Exception check on 'dsytri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsytri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsytri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5530:5: Exception check on 'dsytri2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsytri2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsytri2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5535:5: Exception check on 'dsytri2x' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsytri2x' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsytri2x' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5540:5: Exception check on 'dsytrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsytrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsytrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5545:5: Exception check on 'dsytrs2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dsytrs2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dsytrs2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5550:5: Exception check on 'dtbcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtbcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtbcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5555:5: Exception check on 'dtbrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtbrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtbrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5560:5: Exception check on 'dtbtrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtbtrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtbtrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5565:5: Exception check on 'dtfsm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtfsm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtfsm' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5570:5: Exception check on 'dtftri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtftri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtftri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5575:5: Exception check on 'dtfttp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtfttp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtfttp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5580:5: Exception check on 'dtfttr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtfttr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtfttr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5585:5: Exception check on 'dtgevc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtgevc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtgevc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5590:5: Exception check on 'dtgex2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtgex2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtgex2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5595:5: Exception check on 'dtgexc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtgexc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtgexc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5600:5: Exception check on 'dtgsen' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtgsen' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtgsen' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5605:5: Exception check on 'dtgsja' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtgsja' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtgsja' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5610:5: Exception check on 'dtgsna' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtgsna' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtgsna' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5615:5: Exception check on 'dtgsy2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtgsy2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtgsy2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5620:5: Exception check on 'dtgsyl' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtgsyl' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtgsyl' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5625:5: Exception check on 'dtpcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtpcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtpcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5630:5: Exception check on 'dtpmqrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtpmqrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtpmqrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5635:5: Exception check on 'dtpqrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtpqrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtpqrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5640:5: Exception check on 'dtpqrt2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtpqrt2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtpqrt2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5645:5: Exception check on 'dtprfb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtprfb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtprfb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5650:5: Exception check on 'dtprfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtprfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtprfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5655:5: Exception check on 'dtptri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtptri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtptri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5660:5: Exception check on 'dtptrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtptrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtptrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5665:5: Exception check on 'dtpttf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtpttf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtpttf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5670:5: Exception check on 'dtpttr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtpttr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtpttr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5675:5: Exception check on 'dtrcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtrcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtrcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5680:5: Exception check on 'dtrevc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtrevc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtrevc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5685:5: Exception check on 'dtrexc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtrexc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtrexc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5690:5: Exception check on 'dtrrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtrrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtrrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5695:5: Exception check on 'dtrsen' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtrsen' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtrsen' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5700:5: Exception check on 'dtrsna' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtrsna' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtrsna' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5705:5: Exception check on 'dtrsyl' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtrsyl' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtrsyl' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5710:5: Exception check on 'dtrti2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtrti2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtrti2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5715:5: Exception check on 'dtrtri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtrtri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtrtri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5720:5: Exception check on 'dtrtrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtrtrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtrtrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5725:5: Exception check on 'dtrttf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtrttf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtrttf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5730:5: Exception check on 'dtrttp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtrttp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtrttp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5735:5: Exception check on 'dtzrzf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'dtzrzf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'dtzrzf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5740:5: Exception check on 'ilaver' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ilaver' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ilaver' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5745:5: Exception check on 'sbbcsd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sbbcsd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sbbcsd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5750:5: Exception check on 'sbdsdc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sbdsdc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sbdsdc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5755:5: Exception check on 'sbdsqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sbdsqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sbdsqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5760:5: Exception check on 'sdisna' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sdisna' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sdisna' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5765:5: Exception check on 'sgbbrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgbbrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgbbrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5770:5: Exception check on 'sgbcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgbcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgbcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5775:5: Exception check on 'sgbequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgbequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgbequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5780:5: Exception check on 'sgbequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgbequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgbequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5785:5: Exception check on 'sgbrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgbrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgbrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5790:5: Exception check on 'sgbsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgbsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgbsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5795:5: Exception check on 'sgbsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgbsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgbsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5800:5: Exception check on 'sgbtf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgbtf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgbtf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5805:5: Exception check on 'sgbtrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgbtrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgbtrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5810:5: Exception check on 'sgbtrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgbtrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgbtrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5815:5: Exception check on 'sgebak' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgebak' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgebak' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5820:5: Exception check on 'sgebal' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgebal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgebal' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5825:5: Exception check on 'sgebd2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgebd2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgebd2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5830:5: Exception check on 'sgebrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgebrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgebrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5835:5: Exception check on 'sgecon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgecon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgecon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5840:5: Exception check on 'sgeequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgeequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgeequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5845:5: Exception check on 'sgeequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgeequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgeequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5850:5: Exception check on 'sgees' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgees' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgees' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5855:5: Exception check on 'sgeesx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgeesx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgeesx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5860:5: Exception check on 'sgeev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgeev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgeev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5865:5: Exception check on 'sgeevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgeevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgeevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5870:5: Exception check on 'sgehd2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgehd2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgehd2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5875:5: Exception check on 'sgehrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgehrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgehrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5880:5: Exception check on 'sgejsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgejsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgejsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5885:5: Exception check on 'sgelq2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgelq2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgelq2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5890:5: Exception check on 'sgelqf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgelqf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgelqf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5895:5: Exception check on 'sgels' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgels' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgels' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5900:5: Exception check on 'sgelsd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgelsd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgelsd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5905:5: Exception check on 'sgelss' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgelss' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgelss' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5910:5: Exception check on 'sgelsy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgelsy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgelsy' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5915:5: Exception check on 'sgemqrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgemqrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgemqrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5920:5: Exception check on 'sgeql2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgeql2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgeql2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5925:5: Exception check on 'sgeqlf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgeqlf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgeqlf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5930:5: Exception check on 'sgeqp3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgeqp3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgeqp3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5935:5: Exception check on 'sgeqr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgeqr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgeqr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5940:5: Exception check on 'sgeqr2p' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgeqr2p' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgeqr2p' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5945:5: Exception check on 'sgeqrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgeqrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgeqrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5950:5: Exception check on 'sgeqrfp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgeqrfp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgeqrfp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5955:5: Exception check on 'sgeqrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgeqrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgeqrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5960:5: Exception check on 'sgeqrt2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgeqrt2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgeqrt2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5965:5: Exception check on 'sgeqrt3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgeqrt3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgeqrt3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5970:5: Exception check on 'sgerfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgerfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgerfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5975:5: Exception check on 'sgerq2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgerq2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgerq2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5980:5: Exception check on 'sgerqf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgerqf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgerqf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5985:5: Exception check on 'sgesc2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgesc2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgesc2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5990:5: Exception check on 'sgesdd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgesdd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgesdd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:5995:5: Exception check on 'sgesv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgesv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgesv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6000:5: Exception check on 'sgesvd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgesvd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgesvd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6005:5: Exception check on 'sgesvj' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgesvj' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgesvj' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6010:5: Exception check on 'sgesvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgesvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgesvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6015:5: Exception check on 'sgetc2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgetc2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgetc2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6020:5: Exception check on 'sgetf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgetf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgetf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6025:5: Exception check on 'sgetrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgetrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgetrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6030:5: Exception check on 'sgetri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgetri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgetri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6035:5: Exception check on 'sgetrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgetrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgetrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6040:5: Exception check on 'sggbak' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sggbak' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sggbak' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6045:5: Exception check on 'sggbal' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sggbal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sggbal' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6050:5: Exception check on 'sgges' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgges' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgges' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6055:5: Exception check on 'sggesx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sggesx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sggesx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6060:5: Exception check on 'sggev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sggev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sggev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6065:5: Exception check on 'sggevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sggevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sggevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6070:5: Exception check on 'sggglm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sggglm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sggglm' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6075:5: Exception check on 'sgghrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgghrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgghrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6080:5: Exception check on 'sgglse' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgglse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgglse' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6085:5: Exception check on 'sggqrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sggqrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sggqrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6090:5: Exception check on 'sggrqf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sggrqf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sggrqf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6095:5: Exception check on 'sgsvj0' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgsvj0' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgsvj0' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6100:5: Exception check on 'sgsvj1' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgsvj1' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgsvj1' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6105:5: Exception check on 'sgtcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgtcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgtcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6110:5: Exception check on 'sgtrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgtrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgtrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6115:5: Exception check on 'sgtsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgtsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgtsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6120:5: Exception check on 'sgtsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgtsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgtsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6125:5: Exception check on 'sgttrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgttrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgttrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6130:5: Exception check on 'sgttrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgttrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgttrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6135:5: Exception check on 'sgtts2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sgtts2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sgtts2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6140:5: Exception check on 'shgeqz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'shgeqz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'shgeqz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6145:5: Exception check on 'shsein' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'shsein' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'shsein' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6150:5: Exception check on 'shseqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'shseqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'shseqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6155:5: Exception check on 'slabad' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slabad' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slabad' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6160:5: Exception check on 'slabrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slabrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slabrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6165:5: Exception check on 'slacn2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slacn2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slacn2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6170:5: Exception check on 'slacon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slacon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slacon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6175:5: Exception check on 'slacpy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slacpy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slacpy' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6180:5: Exception check on 'sladiv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sladiv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sladiv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6185:5: Exception check on 'slae2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slae2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slae2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6190:5: Exception check on 'slaebz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaebz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaebz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6195:5: Exception check on 'slaed0' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaed0' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaed0' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6200:5: Exception check on 'slaed1' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaed1' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaed1' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6205:5: Exception check on 'slaed2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaed2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaed2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6210:5: Exception check on 'slaed3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaed3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaed3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6215:5: Exception check on 'slaed4' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaed4' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaed4' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6220:5: Exception check on 'slaed5' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaed5' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaed5' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6225:5: Exception check on 'slaed6' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaed6' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaed6' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6230:5: Exception check on 'slaed7' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaed7' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaed7' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6235:5: Exception check on 'slaed8' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaed8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaed8' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6240:5: Exception check on 'slaed9' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaed9' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaed9' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6245:5: Exception check on 'slaeda' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaeda' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaeda' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6250:5: Exception check on 'slaein' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaein' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaein' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6255:5: Exception check on 'slaev2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaev2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaev2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6260:5: Exception check on 'slaexc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaexc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaexc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6265:5: Exception check on 'slag2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slag2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slag2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6270:5: Exception check on 'slag2d' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slag2d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slag2d' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6275:5: Exception check on 'slags2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slags2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slags2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6280:5: Exception check on 'slagtf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slagtf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slagtf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6285:5: Exception check on 'slagtm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slagtm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slagtm' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6290:5: Exception check on 'slagts' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slagts' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slagts' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6295:5: Exception check on 'slagv2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slagv2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slagv2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6300:5: Exception check on 'slahqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slahqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slahqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6305:5: Exception check on 'slahr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slahr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slahr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6310:5: Exception check on 'slaic1' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaic1' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaic1' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6315:5: Exception check on 'slaln2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaln2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaln2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6320:5: Exception check on 'slals0' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slals0' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slals0' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6325:5: Exception check on 'slalsa' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slalsa' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slalsa' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6330:5: Exception check on 'slalsd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slalsd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slalsd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6335:5: Exception check on 'slamrg' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slamrg' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slamrg' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6340:5: Exception check on 'slanv2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slanv2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slanv2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6345:5: Exception check on 'slapll' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slapll' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slapll' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6350:5: Exception check on 'slapmr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slapmr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slapmr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6355:5: Exception check on 'slapmt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slapmt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slapmt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6360:5: Exception check on 'slaqgb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaqgb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaqgb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6365:5: Exception check on 'slaqge' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaqge' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaqge' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6370:5: Exception check on 'slaqp2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaqp2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaqp2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6375:5: Exception check on 'slaqps' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaqps' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaqps' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6380:5: Exception check on 'slaqr0' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaqr0' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaqr0' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6385:5: Exception check on 'slaqr1' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaqr1' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaqr1' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6390:5: Exception check on 'slaqr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaqr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaqr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6395:5: Exception check on 'slaqr3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaqr3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaqr3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6400:5: Exception check on 'slaqr4' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaqr4' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaqr4' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6405:5: Exception check on 'slaqr5' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaqr5' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaqr5' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6410:5: Exception check on 'slaqsb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaqsb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaqsb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6415:5: Exception check on 'slaqsp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaqsp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaqsp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6420:5: Exception check on 'slaqsy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaqsy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaqsy' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6425:5: Exception check on 'slaqtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaqtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaqtr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6430:5: Exception check on 'slar1v' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slar1v' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slar1v' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6435:5: Exception check on 'slar2v' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slar2v' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slar2v' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6440:5: Exception check on 'slarf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6445:5: Exception check on 'slarfb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarfb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarfb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6450:5: Exception check on 'slarfg' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarfg' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarfg' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6455:5: Exception check on 'slarfgp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarfgp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarfgp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6460:5: Exception check on 'slarft' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarft' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarft' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6465:5: Exception check on 'slarfx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarfx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarfx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6470:5: Exception check on 'slargv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slargv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slargv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6475:5: Exception check on 'slarnv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarnv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarnv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6480:5: Exception check on 'slarra' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarra' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarra' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6485:5: Exception check on 'slarrb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarrb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarrb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6490:5: Exception check on 'slarrc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarrc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarrc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6495:5: Exception check on 'slarrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6500:5: Exception check on 'slarre' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarre' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarre' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6505:5: Exception check on 'slarrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6510:5: Exception check on 'slarrj' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarrj' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarrj' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6515:5: Exception check on 'slarrk' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarrk' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarrk' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6520:5: Exception check on 'slarrr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarrr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarrr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6525:5: Exception check on 'slarrv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarrv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarrv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6530:5: Exception check on 'slartg' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slartg' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slartg' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6535:5: Exception check on 'slartgp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slartgp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slartgp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6540:5: Exception check on 'slartgs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slartgs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slartgs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6545:5: Exception check on 'slartv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slartv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slartv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6550:5: Exception check on 'slaruv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaruv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaruv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6555:5: Exception check on 'slarz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6560:5: Exception check on 'slarzb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarzb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarzb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6565:5: Exception check on 'slarzt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slarzt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slarzt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6570:5: Exception check on 'slas2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slas2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slas2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6575:5: Exception check on 'slascl' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slascl' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slascl' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6580:5: Exception check on 'slasd0' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasd0' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasd0' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6585:5: Exception check on 'slasd1' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasd1' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasd1' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6590:5: Exception check on 'slasd2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasd2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasd2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6595:5: Exception check on 'slasd3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasd3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasd3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6600:5: Exception check on 'slasd4' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasd4' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasd4' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6605:5: Exception check on 'slasd5' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasd5' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasd5' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6610:5: Exception check on 'slasd6' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasd6' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasd6' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6615:5: Exception check on 'slasd7' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasd7' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasd7' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6620:5: Exception check on 'slasd8' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasd8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasd8' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6625:5: Exception check on 'slasda' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasda' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasda' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6630:5: Exception check on 'slasdq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasdq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasdq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6635:5: Exception check on 'slasdt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasdt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasdt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6640:5: Exception check on 'slaset' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaset' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaset' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6645:5: Exception check on 'slasq1' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasq1' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasq1' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6650:5: Exception check on 'slasq2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasq2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasq2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6655:5: Exception check on 'slasq3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasq3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasq3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6660:5: Exception check on 'slasq4' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasq4' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasq4' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6665:5: Exception check on 'slasq6' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasq6' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasq6' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6670:5: Exception check on 'slasr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6675:5: Exception check on 'slasrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6680:5: Exception check on 'slassq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slassq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slassq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6685:5: Exception check on 'slasv2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasv2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasv2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6690:5: Exception check on 'slaswp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slaswp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slaswp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6695:5: Exception check on 'slasy2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasy2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasy2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6700:5: Exception check on 'slasyf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slasyf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slasyf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6705:5: Exception check on 'slatbs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slatbs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slatbs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6710:5: Exception check on 'slatdf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slatdf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slatdf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6715:5: Exception check on 'slatps' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slatps' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slatps' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6720:5: Exception check on 'slatrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slatrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slatrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6725:5: Exception check on 'slatrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slatrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slatrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6730:5: Exception check on 'slatrz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slatrz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slatrz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6735:5: Exception check on 'slauu2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slauu2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slauu2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6740:5: Exception check on 'slauum' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'slauum' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'slauum' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6745:5: Exception check on 'sopgtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sopgtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sopgtr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6750:5: Exception check on 'sopmtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sopmtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sopmtr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6755:5: Exception check on 'sorbdb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sorbdb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sorbdb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6760:5: Exception check on 'sorcsd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sorcsd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sorcsd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6765:5: Exception check on 'sorg2l' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sorg2l' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sorg2l' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6770:5: Exception check on 'sorg2r' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sorg2r' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sorg2r' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6775:5: Exception check on 'sorgbr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sorgbr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sorgbr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6780:5: Exception check on 'sorghr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sorghr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sorghr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6785:5: Exception check on 'sorgl2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sorgl2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sorgl2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6790:5: Exception check on 'sorglq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sorglq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sorglq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6795:5: Exception check on 'sorgql' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sorgql' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sorgql' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6800:5: Exception check on 'sorgqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sorgqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sorgqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6805:5: Exception check on 'sorgr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sorgr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sorgr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6810:5: Exception check on 'sorgrq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sorgrq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sorgrq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6815:5: Exception check on 'sorgtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sorgtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sorgtr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6820:5: Exception check on 'sorm2l' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sorm2l' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sorm2l' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6825:5: Exception check on 'sorm2r' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sorm2r' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sorm2r' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6830:5: Exception check on 'sormbr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sormbr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sormbr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6835:5: Exception check on 'sormhr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sormhr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sormhr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6840:5: Exception check on 'sorml2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sorml2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sorml2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6845:5: Exception check on 'sormlq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sormlq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sormlq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6850:5: Exception check on 'sormql' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sormql' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sormql' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6855:5: Exception check on 'sormqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sormqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sormqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6860:5: Exception check on 'sormr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sormr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sormr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6865:5: Exception check on 'sormr3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sormr3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sormr3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6870:5: Exception check on 'sormrq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sormrq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sormrq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6875:5: Exception check on 'sormrz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sormrz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sormrz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6880:5: Exception check on 'sormtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sormtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sormtr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6885:5: Exception check on 'spbcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spbcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spbcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6890:5: Exception check on 'spbequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spbequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spbequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6895:5: Exception check on 'spbrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spbrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spbrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6900:5: Exception check on 'spbstf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spbstf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spbstf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6905:5: Exception check on 'spbsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spbsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spbsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6910:5: Exception check on 'spbsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spbsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spbsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6915:5: Exception check on 'spbtf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spbtf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spbtf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6920:5: Exception check on 'spbtrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spbtrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spbtrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6925:5: Exception check on 'spbtrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spbtrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spbtrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6930:5: Exception check on 'spftrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spftrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spftrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6935:5: Exception check on 'spftri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spftri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spftri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6940:5: Exception check on 'spftrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spftrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spftrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6945:5: Exception check on 'spocon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spocon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spocon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6950:5: Exception check on 'spoequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spoequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spoequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6955:5: Exception check on 'spoequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spoequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spoequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6960:5: Exception check on 'sporfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sporfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sporfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6965:5: Exception check on 'sposv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sposv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sposv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6970:5: Exception check on 'sposvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sposvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sposvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6975:5: Exception check on 'spotf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spotf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spotf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6980:5: Exception check on 'spotrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spotrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spotrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6985:5: Exception check on 'spotri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spotri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spotri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6990:5: Exception check on 'spotrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spotrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spotrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:6995:5: Exception check on 'sppcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sppcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sppcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7000:5: Exception check on 'sppequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sppequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sppequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7005:5: Exception check on 'spprfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spprfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spprfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7010:5: Exception check on 'sppsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sppsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sppsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7015:5: Exception check on 'sppsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sppsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sppsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7020:5: Exception check on 'spptrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spptrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spptrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7025:5: Exception check on 'spptri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spptri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spptri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7030:5: Exception check on 'spptrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spptrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spptrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7035:5: Exception check on 'spstf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spstf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spstf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7040:5: Exception check on 'spstrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spstrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spstrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7045:5: Exception check on 'sptcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sptcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sptcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7050:5: Exception check on 'spteqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spteqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spteqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7055:5: Exception check on 'sptrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sptrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sptrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7060:5: Exception check on 'sptsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sptsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sptsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7065:5: Exception check on 'sptsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sptsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sptsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7070:5: Exception check on 'spttrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spttrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spttrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7075:5: Exception check on 'spttrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'spttrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'spttrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7080:5: Exception check on 'sptts2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sptts2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sptts2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7085:5: Exception check on 'srscl' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'srscl' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'srscl' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7090:5: Exception check on 'ssbev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssbev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssbev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7095:5: Exception check on 'ssbevd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssbevd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssbevd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7100:5: Exception check on 'ssbevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssbevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssbevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7105:5: Exception check on 'ssbgst' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssbgst' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssbgst' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7110:5: Exception check on 'ssbgv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssbgv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssbgv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7115:5: Exception check on 'ssbgvd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssbgvd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssbgvd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7120:5: Exception check on 'ssbgvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssbgvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssbgvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7125:5: Exception check on 'ssbtrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssbtrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssbtrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7130:5: Exception check on 'ssfrk' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssfrk' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssfrk' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7135:5: Exception check on 'sspcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sspcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sspcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7140:5: Exception check on 'sspev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sspev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sspev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7145:5: Exception check on 'sspevd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sspevd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sspevd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7150:5: Exception check on 'sspevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sspevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sspevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7155:5: Exception check on 'sspgst' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sspgst' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sspgst' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7160:5: Exception check on 'sspgv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sspgv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sspgv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7165:5: Exception check on 'sspgvd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sspgvd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sspgvd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7170:5: Exception check on 'sspgvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sspgvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sspgvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7175:5: Exception check on 'ssprfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssprfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssprfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7180:5: Exception check on 'sspsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sspsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sspsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7185:5: Exception check on 'sspsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sspsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sspsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7190:5: Exception check on 'ssptrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssptrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssptrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7195:5: Exception check on 'ssptrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssptrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssptrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7200:5: Exception check on 'ssptri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssptri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssptri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7205:5: Exception check on 'ssptrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssptrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssptrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7210:5: Exception check on 'sstebz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sstebz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sstebz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7215:5: Exception check on 'sstedc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sstedc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sstedc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7220:5: Exception check on 'sstegr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sstegr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sstegr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7225:5: Exception check on 'sstein' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sstein' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sstein' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7230:5: Exception check on 'sstemr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sstemr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sstemr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7235:5: Exception check on 'ssteqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssteqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssteqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7240:5: Exception check on 'ssterf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssterf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssterf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7245:5: Exception check on 'sstev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sstev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sstev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7250:5: Exception check on 'sstevd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sstevd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sstevd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7255:5: Exception check on 'sstevr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sstevr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sstevr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7260:5: Exception check on 'sstevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'sstevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'sstevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7265:5: Exception check on 'ssycon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssycon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssycon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7270:5: Exception check on 'ssyconv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssyconv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssyconv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7275:5: Exception check on 'ssyequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssyequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssyequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7280:5: Exception check on 'ssyev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssyev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssyev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7285:5: Exception check on 'ssyevd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssyevd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssyevd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7290:5: Exception check on 'ssyevr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssyevr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssyevr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7295:5: Exception check on 'ssyevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssyevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssyevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7300:5: Exception check on 'ssygs2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssygs2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssygs2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7305:5: Exception check on 'ssygst' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssygst' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssygst' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7310:5: Exception check on 'ssygv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssygv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssygv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7315:5: Exception check on 'ssygvd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssygvd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssygvd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7320:5: Exception check on 'ssygvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssygvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssygvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7325:5: Exception check on 'ssyrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssyrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssyrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7330:5: Exception check on 'ssysv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssysv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssysv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7335:5: Exception check on 'ssysvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssysvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssysvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7340:5: Exception check on 'ssyswapr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssyswapr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssyswapr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7345:5: Exception check on 'ssytd2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssytd2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssytd2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7350:5: Exception check on 'ssytf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssytf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssytf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7355:5: Exception check on 'ssytrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssytrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssytrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7360:5: Exception check on 'ssytrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssytrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssytrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7365:5: Exception check on 'ssytri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssytri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssytri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7370:5: Exception check on 'ssytri2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssytri2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssytri2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7375:5: Exception check on 'ssytri2x' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssytri2x' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssytri2x' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7380:5: Exception check on 'ssytrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssytrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssytrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7385:5: Exception check on 'ssytrs2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ssytrs2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ssytrs2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7390:5: Exception check on 'stbcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stbcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stbcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7395:5: Exception check on 'stbrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stbrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stbrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7400:5: Exception check on 'stbtrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stbtrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stbtrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7405:5: Exception check on 'stfsm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stfsm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stfsm' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7410:5: Exception check on 'stftri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stftri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stftri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7415:5: Exception check on 'stfttp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stfttp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stfttp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7420:5: Exception check on 'stfttr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stfttr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stfttr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7425:5: Exception check on 'stgevc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stgevc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stgevc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7430:5: Exception check on 'stgex2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stgex2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stgex2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7435:5: Exception check on 'stgexc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stgexc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stgexc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7440:5: Exception check on 'stgsen' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stgsen' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stgsen' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7445:5: Exception check on 'stgsja' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stgsja' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stgsja' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7450:5: Exception check on 'stgsna' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stgsna' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stgsna' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7455:5: Exception check on 'stgsy2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stgsy2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stgsy2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7460:5: Exception check on 'stgsyl' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stgsyl' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stgsyl' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7465:5: Exception check on 'stpcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stpcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stpcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7470:5: Exception check on 'stpmqrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stpmqrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stpmqrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7475:5: Exception check on 'stpqrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stpqrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stpqrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7480:5: Exception check on 'stpqrt2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stpqrt2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stpqrt2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7485:5: Exception check on 'stprfb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stprfb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stprfb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7490:5: Exception check on 'stprfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stprfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stprfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7495:5: Exception check on 'stptri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stptri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stptri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7500:5: Exception check on 'stptrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stptrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stptrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7505:5: Exception check on 'stpttf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stpttf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stpttf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7510:5: Exception check on 'stpttr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stpttr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stpttr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7515:5: Exception check on 'strcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'strcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'strcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7520:5: Exception check on 'strevc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'strevc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'strevc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7525:5: Exception check on 'strexc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'strexc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'strexc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7530:5: Exception check on 'strrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'strrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'strrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7535:5: Exception check on 'strsen' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'strsen' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'strsen' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7540:5: Exception check on 'strsna' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'strsna' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'strsna' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7545:5: Exception check on 'strsyl' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'strsyl' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'strsyl' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7550:5: Exception check on 'strti2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'strti2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'strti2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7555:5: Exception check on 'strtri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'strtri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'strtri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7560:5: Exception check on 'strtrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'strtrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'strtrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7565:5: Exception check on 'strttf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'strttf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'strttf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7570:5: Exception check on 'strttp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'strttp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'strttp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7575:5: Exception check on 'stzrzf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'stzrzf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'stzrzf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7580:5: Exception check on 'xerbla_array' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'xerbla_array' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'xerbla_array' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7585:5: Exception check on 'zbbcsd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zbbcsd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zbbcsd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7590:5: Exception check on 'zbdsqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zbdsqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zbdsqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7595:5: Exception check on 'zcgesv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zcgesv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zcgesv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7600:5: Exception check on 'zcposv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zcposv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zcposv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7605:5: Exception check on 'zdrscl' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zdrscl' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zdrscl' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7610:5: Exception check on 'zgbbrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgbbrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgbbrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7615:5: Exception check on 'zgbcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgbcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgbcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7620:5: Exception check on 'zgbequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgbequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgbequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7625:5: Exception check on 'zgbequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgbequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgbequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7630:5: Exception check on 'zgbrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgbrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgbrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7635:5: Exception check on 'zgbsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgbsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgbsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7640:5: Exception check on 'zgbsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgbsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgbsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7645:5: Exception check on 'zgbtf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgbtf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgbtf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7650:5: Exception check on 'zgbtrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgbtrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgbtrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7655:5: Exception check on 'zgbtrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgbtrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgbtrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7660:5: Exception check on 'zgebak' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgebak' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgebak' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7665:5: Exception check on 'zgebal' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgebal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgebal' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7670:5: Exception check on 'zgebd2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgebd2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgebd2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7675:5: Exception check on 'zgebrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgebrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgebrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7680:5: Exception check on 'zgecon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgecon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgecon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7685:5: Exception check on 'zgeequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgeequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgeequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7690:5: Exception check on 'zgeequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgeequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgeequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7695:5: Exception check on 'zgees' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgees' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgees' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7700:5: Exception check on 'zgeesx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgeesx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgeesx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7705:5: Exception check on 'zgeev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgeev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgeev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7710:5: Exception check on 'zgeevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgeevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgeevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7715:5: Exception check on 'zgehd2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgehd2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgehd2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7720:5: Exception check on 'zgehrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgehrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgehrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7725:5: Exception check on 'zgelq2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgelq2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgelq2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7730:5: Exception check on 'zgelqf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgelqf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgelqf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7735:5: Exception check on 'zgels' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgels' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgels' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7740:5: Exception check on 'zgelsd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgelsd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgelsd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7745:5: Exception check on 'zgelss' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgelss' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgelss' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7750:5: Exception check on 'zgelsy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgelsy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgelsy' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7755:5: Exception check on 'zgemqrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgemqrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgemqrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7760:5: Exception check on 'zgeql2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgeql2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgeql2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7765:5: Exception check on 'zgeqlf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgeqlf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgeqlf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7770:5: Exception check on 'zgeqp3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgeqp3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgeqp3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7775:5: Exception check on 'zgeqr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgeqr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgeqr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7780:5: Exception check on 'zgeqr2p' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgeqr2p' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgeqr2p' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7785:5: Exception check on 'zgeqrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgeqrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgeqrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7790:5: Exception check on 'zgeqrfp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgeqrfp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgeqrfp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7795:5: Exception check on 'zgeqrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgeqrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgeqrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7800:5: Exception check on 'zgeqrt2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgeqrt2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgeqrt2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7805:5: Exception check on 'zgeqrt3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgeqrt3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgeqrt3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7810:5: Exception check on 'zgerfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgerfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgerfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7815:5: Exception check on 'zgerq2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgerq2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgerq2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7820:5: Exception check on 'zgerqf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgerqf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgerqf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7825:5: Exception check on 'zgesc2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgesc2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgesc2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7830:5: Exception check on 'zgesdd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgesdd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgesdd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7835:5: Exception check on 'zgesv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgesv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgesv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7840:5: Exception check on 'zgesvd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgesvd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgesvd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7845:5: Exception check on 'zgesvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgesvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgesvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7850:5: Exception check on 'zgetc2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgetc2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgetc2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7855:5: Exception check on 'zgetf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgetf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgetf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7860:5: Exception check on 'zgetrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgetrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgetrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7865:5: Exception check on 'zgetri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgetri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgetri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7870:5: Exception check on 'zgetrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgetrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgetrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7875:5: Exception check on 'zggbak' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zggbak' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zggbak' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7880:5: Exception check on 'zggbal' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zggbal' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zggbal' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7885:5: Exception check on 'zgges' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgges' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgges' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7890:5: Exception check on 'zggesx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zggesx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zggesx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7895:5: Exception check on 'zggev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zggev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zggev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7900:5: Exception check on 'zggevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zggevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zggevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7905:5: Exception check on 'zggglm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zggglm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zggglm' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7910:5: Exception check on 'zgghrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgghrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgghrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7915:5: Exception check on 'zgglse' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgglse' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgglse' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7920:5: Exception check on 'zggqrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zggqrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zggqrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7925:5: Exception check on 'zggrqf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zggrqf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zggrqf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7930:5: Exception check on 'zgtcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgtcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgtcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7935:5: Exception check on 'zgtrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgtrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgtrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7940:5: Exception check on 'zgtsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgtsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgtsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7945:5: Exception check on 'zgtsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgtsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgtsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7950:5: Exception check on 'zgttrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgttrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgttrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7955:5: Exception check on 'zgttrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgttrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgttrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7960:5: Exception check on 'zgtts2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zgtts2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zgtts2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7965:5: Exception check on 'zhbev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhbev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhbev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7970:5: Exception check on 'zhbevd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhbevd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhbevd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7975:5: Exception check on 'zhbevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhbevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhbevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7980:5: Exception check on 'zhbgst' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhbgst' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhbgst' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7985:5: Exception check on 'zhbgv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhbgv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhbgv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7990:5: Exception check on 'zhbgvd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhbgvd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhbgvd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:7995:5: Exception check on 'zhbgvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhbgvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhbgvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8000:5: Exception check on 'zhbtrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhbtrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhbtrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8005:5: Exception check on 'zhecon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhecon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhecon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8010:5: Exception check on 'zheequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zheequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zheequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8015:5: Exception check on 'zheev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zheev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zheev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8020:5: Exception check on 'zheevd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zheevd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zheevd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8025:5: Exception check on 'zheevr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zheevr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zheevr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8030:5: Exception check on 'zheevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zheevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zheevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8035:5: Exception check on 'zhegs2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhegs2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhegs2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8040:5: Exception check on 'zhegst' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhegst' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhegst' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8045:5: Exception check on 'zhegv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhegv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhegv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8050:5: Exception check on 'zhegvd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhegvd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhegvd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8055:5: Exception check on 'zhegvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhegvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhegvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8060:5: Exception check on 'zherfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zherfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zherfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8065:5: Exception check on 'zhesv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhesv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhesv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8070:5: Exception check on 'zhesvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhesvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhesvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8075:5: Exception check on 'zheswapr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zheswapr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zheswapr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8080:5: Exception check on 'zhetd2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhetd2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhetd2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8085:5: Exception check on 'zhetf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhetf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhetf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8090:5: Exception check on 'zhetrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhetrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhetrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8095:5: Exception check on 'zhetrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhetrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhetrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8100:5: Exception check on 'zhetri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhetri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhetri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8105:5: Exception check on 'zhetri2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhetri2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhetri2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8110:5: Exception check on 'zhetri2x' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhetri2x' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhetri2x' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8115:5: Exception check on 'zhetrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhetrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhetrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8120:5: Exception check on 'zhetrs2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhetrs2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhetrs2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8125:5: Exception check on 'zhfrk' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhfrk' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhfrk' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8130:5: Exception check on 'zhgeqz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhgeqz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhgeqz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8135:5: Exception check on 'zhpcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhpcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhpcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8140:5: Exception check on 'zhpev' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhpev' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhpev' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8145:5: Exception check on 'zhpevd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhpevd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhpevd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8150:5: Exception check on 'zhpevx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhpevx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhpevx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8155:5: Exception check on 'zhpgst' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhpgst' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhpgst' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8160:5: Exception check on 'zhpgv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhpgv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhpgv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8165:5: Exception check on 'zhpgvd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhpgvd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhpgvd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8170:5: Exception check on 'zhpgvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhpgvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhpgvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8175:5: Exception check on 'zhprfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhprfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhprfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8180:5: Exception check on 'zhpsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhpsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhpsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8185:5: Exception check on 'zhpsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhpsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhpsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8190:5: Exception check on 'zhptrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhptrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhptrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8195:5: Exception check on 'zhptrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhptrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhptrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8200:5: Exception check on 'zhptri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhptri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhptri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8205:5: Exception check on 'zhptrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhptrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhptrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8210:5: Exception check on 'zhsein' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhsein' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhsein' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8215:5: Exception check on 'zhseqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zhseqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zhseqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8220:5: Exception check on 'zlabrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlabrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlabrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8225:5: Exception check on 'zlacgv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlacgv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlacgv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8230:5: Exception check on 'zlacn2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlacn2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlacn2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8235:5: Exception check on 'zlacon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlacon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlacon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8240:5: Exception check on 'zlacp2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlacp2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlacp2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8245:5: Exception check on 'zlacpy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlacpy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlacpy' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8250:5: Exception check on 'zlacrm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlacrm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlacrm' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8255:5: Exception check on 'zlacrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlacrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlacrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8260:5: Exception check on 'zlaed0' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaed0' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaed0' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8265:5: Exception check on 'zlaed7' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaed7' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaed7' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8270:5: Exception check on 'zlaed8' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaed8' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaed8' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8275:5: Exception check on 'zlaein' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaein' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaein' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8280:5: Exception check on 'zlaesy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaesy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaesy' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8285:5: Exception check on 'zlaev2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaev2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaev2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8290:5: Exception check on 'zlag2c' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlag2c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlag2c' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8295:5: Exception check on 'zlags2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlags2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlags2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8300:5: Exception check on 'zlagtm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlagtm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlagtm' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8305:5: Exception check on 'zlahef' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlahef' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlahef' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8310:5: Exception check on 'zlahqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlahqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlahqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8315:5: Exception check on 'zlahr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlahr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlahr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8320:5: Exception check on 'zlaic1' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaic1' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaic1' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8325:5: Exception check on 'zlals0' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlals0' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlals0' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8330:5: Exception check on 'zlalsa' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlalsa' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlalsa' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8335:5: Exception check on 'zlalsd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlalsd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlalsd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8340:5: Exception check on 'zlapll' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlapll' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlapll' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8345:5: Exception check on 'zlapmr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlapmr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlapmr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8350:5: Exception check on 'zlapmt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlapmt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlapmt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8355:5: Exception check on 'zlaqgb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaqgb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaqgb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8360:5: Exception check on 'zlaqge' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaqge' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaqge' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8365:5: Exception check on 'zlaqhb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaqhb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaqhb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8370:5: Exception check on 'zlaqhe' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaqhe' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaqhe' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8375:5: Exception check on 'zlaqhp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaqhp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaqhp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8380:5: Exception check on 'zlaqp2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaqp2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaqp2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8385:5: Exception check on 'zlaqps' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaqps' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaqps' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8390:5: Exception check on 'zlaqr0' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaqr0' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaqr0' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8395:5: Exception check on 'zlaqr1' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaqr1' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaqr1' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8400:5: Exception check on 'zlaqr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaqr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaqr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8405:5: Exception check on 'zlaqr3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaqr3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaqr3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8410:5: Exception check on 'zlaqr4' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaqr4' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaqr4' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8415:5: Exception check on 'zlaqr5' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaqr5' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaqr5' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8420:5: Exception check on 'zlaqsb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaqsb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaqsb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8425:5: Exception check on 'zlaqsp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaqsp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaqsp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8430:5: Exception check on 'zlaqsy' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaqsy' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaqsy' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8435:5: Exception check on 'zlar1v' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlar1v' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlar1v' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8440:5: Exception check on 'zlar2v' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlar2v' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlar2v' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8445:5: Exception check on 'zlarcm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlarcm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlarcm' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8450:5: Exception check on 'zlarf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlarf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlarf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8455:5: Exception check on 'zlarfb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlarfb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlarfb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8460:5: Exception check on 'zlarfg' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlarfg' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlarfg' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8465:5: Exception check on 'zlarfgp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlarfgp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlarfgp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8470:5: Exception check on 'zlarft' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlarft' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlarft' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8475:5: Exception check on 'zlarfx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlarfx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlarfx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8480:5: Exception check on 'zlargv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlargv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlargv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8485:5: Exception check on 'zlarnv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlarnv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlarnv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8490:5: Exception check on 'zlarrv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlarrv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlarrv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8495:5: Exception check on 'zlartg' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlartg' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlartg' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8500:5: Exception check on 'zlartv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlartv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlartv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8505:5: Exception check on 'zlarz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlarz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlarz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8510:5: Exception check on 'zlarzb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlarzb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlarzb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8515:5: Exception check on 'zlarzt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlarzt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlarzt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8520:5: Exception check on 'zlascl' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlascl' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlascl' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8525:5: Exception check on 'zlaset' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaset' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaset' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8530:5: Exception check on 'zlasr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlasr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlasr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8535:5: Exception check on 'zlassq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlassq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlassq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8540:5: Exception check on 'zlaswp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlaswp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlaswp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8545:5: Exception check on 'zlasyf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlasyf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlasyf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8550:5: Exception check on 'zlat2c' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlat2c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlat2c' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8555:5: Exception check on 'zlatbs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlatbs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlatbs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8560:5: Exception check on 'zlatdf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlatdf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlatdf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8565:5: Exception check on 'zlatps' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlatps' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlatps' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8570:5: Exception check on 'zlatrd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlatrd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlatrd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8575:5: Exception check on 'zlatrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlatrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlatrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8580:5: Exception check on 'zlatrz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlatrz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlatrz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8585:5: Exception check on 'zlauu2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlauu2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlauu2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8590:5: Exception check on 'zlauum' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zlauum' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zlauum' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8595:5: Exception check on 'zpbcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpbcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpbcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8600:5: Exception check on 'zpbequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpbequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpbequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8605:5: Exception check on 'zpbrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpbrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpbrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8610:5: Exception check on 'zpbstf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpbstf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpbstf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8615:5: Exception check on 'zpbsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpbsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpbsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8620:5: Exception check on 'zpbsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpbsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpbsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8625:5: Exception check on 'zpbtf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpbtf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpbtf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8630:5: Exception check on 'zpbtrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpbtrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpbtrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8635:5: Exception check on 'zpbtrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpbtrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpbtrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8640:5: Exception check on 'zpftrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpftrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpftrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8645:5: Exception check on 'zpftri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpftri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpftri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8650:5: Exception check on 'zpftrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpftrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpftrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8655:5: Exception check on 'zpocon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpocon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpocon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8660:5: Exception check on 'zpoequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpoequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpoequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8665:5: Exception check on 'zpoequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpoequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpoequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8670:5: Exception check on 'zporfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zporfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zporfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8675:5: Exception check on 'zposv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zposv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zposv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8680:5: Exception check on 'zposvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zposvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zposvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8685:5: Exception check on 'zpotf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpotf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpotf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8690:5: Exception check on 'zpotrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpotrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpotrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8695:5: Exception check on 'zpotri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpotri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpotri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8700:5: Exception check on 'zpotrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpotrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpotrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8705:5: Exception check on 'zppcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zppcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zppcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8710:5: Exception check on 'zppequ' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zppequ' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zppequ' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8715:5: Exception check on 'zpprfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpprfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpprfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8720:5: Exception check on 'zppsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zppsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zppsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8725:5: Exception check on 'zppsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zppsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zppsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8730:5: Exception check on 'zpptrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpptrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpptrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8735:5: Exception check on 'zpptri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpptri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpptri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8740:5: Exception check on 'zpptrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpptrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpptrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8745:5: Exception check on 'zpstf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpstf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpstf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8750:5: Exception check on 'zpstrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpstrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpstrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8755:5: Exception check on 'zptcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zptcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zptcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8760:5: Exception check on 'zpteqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpteqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpteqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8765:5: Exception check on 'zptrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zptrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zptrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8770:5: Exception check on 'zptsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zptsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zptsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8775:5: Exception check on 'zptsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zptsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zptsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8780:5: Exception check on 'zpttrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpttrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpttrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8785:5: Exception check on 'zpttrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zpttrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zpttrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8790:5: Exception check on 'zptts2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zptts2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zptts2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8795:5: Exception check on 'zrot' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zrot' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zrot' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8800:5: Exception check on 'zspcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zspcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zspcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8805:5: Exception check on 'zspmv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zspmv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zspmv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8810:5: Exception check on 'zspr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zspr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zspr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8815:5: Exception check on 'zsprfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsprfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsprfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8820:5: Exception check on 'zspsv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zspsv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zspsv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8825:5: Exception check on 'zspsvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zspsvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zspsvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8830:5: Exception check on 'zsptrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsptrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsptrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8835:5: Exception check on 'zsptri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsptri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsptri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8840:5: Exception check on 'zsptrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsptrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsptrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8845:5: Exception check on 'zstedc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zstedc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zstedc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8850:5: Exception check on 'zstegr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zstegr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zstegr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8855:5: Exception check on 'zstein' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zstein' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zstein' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8860:5: Exception check on 'zstemr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zstemr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zstemr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8865:5: Exception check on 'zsteqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsteqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsteqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8870:5: Exception check on 'zsycon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsycon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsycon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8875:5: Exception check on 'zsyconv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsyconv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsyconv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8880:5: Exception check on 'zsyequb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsyequb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsyequb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8885:5: Exception check on 'zsymv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsymv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsymv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8890:5: Exception check on 'zsyr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsyr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsyr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8895:5: Exception check on 'zsyrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsyrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsyrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8900:5: Exception check on 'zsysv' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsysv' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsysv' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8905:5: Exception check on 'zsysvx' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsysvx' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsysvx' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8910:5: Exception check on 'zsyswapr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsyswapr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsyswapr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8915:5: Exception check on 'zsytf2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsytf2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsytf2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8920:5: Exception check on 'zsytrf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsytrf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsytrf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8925:5: Exception check on 'zsytri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsytri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsytri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8930:5: Exception check on 'zsytri2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsytri2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsytri2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8935:5: Exception check on 'zsytri2x' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsytri2x' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsytri2x' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8940:5: Exception check on 'zsytrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsytrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsytrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8945:5: Exception check on 'zsytrs2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zsytrs2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zsytrs2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8950:5: Exception check on 'ztbcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztbcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztbcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8955:5: Exception check on 'ztbrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztbrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztbrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8960:5: Exception check on 'ztbtrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztbtrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztbtrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8965:5: Exception check on 'ztfsm' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztfsm' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztfsm' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8970:5: Exception check on 'ztftri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztftri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztftri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8975:5: Exception check on 'ztfttp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztfttp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztfttp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8980:5: Exception check on 'ztfttr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztfttr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztfttr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8985:5: Exception check on 'ztgevc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztgevc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztgevc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8990:5: Exception check on 'ztgex2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztgex2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztgex2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:8995:5: Exception check on 'ztgexc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztgexc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztgexc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9000:5: Exception check on 'ztgsen' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztgsen' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztgsen' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9005:5: Exception check on 'ztgsja' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztgsja' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztgsja' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9010:5: Exception check on 'ztgsna' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztgsna' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztgsna' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9015:5: Exception check on 'ztgsy2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztgsy2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztgsy2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9020:5: Exception check on 'ztgsyl' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztgsyl' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztgsyl' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9025:5: Exception check on 'ztpcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztpcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztpcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9030:5: Exception check on 'ztpmqrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztpmqrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztpmqrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9035:5: Exception check on 'ztpqrt' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztpqrt' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztpqrt' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9040:5: Exception check on 'ztpqrt2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztpqrt2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztpqrt2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9045:5: Exception check on 'ztprfb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztprfb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztprfb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9050:5: Exception check on 'ztprfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztprfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztprfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9055:5: Exception check on 'ztptri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztptri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztptri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9060:5: Exception check on 'ztptrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztptrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztptrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9065:5: Exception check on 'ztpttf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztpttf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztpttf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9070:5: Exception check on 'ztpttr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztpttr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztpttr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9075:5: Exception check on 'ztrcon' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztrcon' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztrcon' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9080:5: Exception check on 'ztrevc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztrevc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztrevc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9085:5: Exception check on 'ztrexc' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztrexc' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztrexc' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9090:5: Exception check on 'ztrrfs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztrrfs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztrrfs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9095:5: Exception check on 'ztrsen' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztrsen' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztrsen' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9100:5: Exception check on 'ztrsna' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztrsna' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztrsna' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9105:5: Exception check on 'ztrsyl' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztrsyl' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztrsyl' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9110:5: Exception check on 'ztrti2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztrti2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztrti2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9115:5: Exception check on 'ztrtri' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztrtri' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztrtri' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9120:5: Exception check on 'ztrtrs' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztrtrs' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztrtrs' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9125:5: Exception check on 'ztrttf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztrttf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztrttf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9130:5: Exception check on 'ztrttp' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztrttp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztrttp' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9135:5: Exception check on 'ztzrzf' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'ztzrzf' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'ztzrzf' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9140:5: Exception check on 'zunbdb' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zunbdb' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zunbdb' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9145:5: Exception check on 'zuncsd' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zuncsd' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zuncsd' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9150:5: Exception check on 'zung2l' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zung2l' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zung2l' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9155:5: Exception check on 'zung2r' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zung2r' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zung2r' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9160:5: Exception check on 'zungbr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zungbr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zungbr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9165:5: Exception check on 'zunghr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zunghr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zunghr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9170:5: Exception check on 'zungl2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zungl2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zungl2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9175:5: Exception check on 'zunglq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zunglq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zunglq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9180:5: Exception check on 'zungql' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zungql' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zungql' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9185:5: Exception check on 'zungqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zungqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zungqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9190:5: Exception check on 'zungr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zungr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zungr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9195:5: Exception check on 'zungrq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zungrq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zungrq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9200:5: Exception check on 'zungtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zungtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zungtr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9205:5: Exception check on 'zunm2l' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zunm2l' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zunm2l' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9210:5: Exception check on 'zunm2r' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zunm2r' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zunm2r' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9215:5: Exception check on 'zunmbr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zunmbr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zunmbr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9220:5: Exception check on 'zunmhr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zunmhr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zunmhr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9225:5: Exception check on 'zunml2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zunml2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zunml2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9230:5: Exception check on 'zunmlq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zunmlq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zunmlq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9235:5: Exception check on 'zunmql' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zunmql' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zunmql' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9240:5: Exception check on 'zunmqr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zunmqr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zunmqr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9245:5: Exception check on 'zunmr2' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zunmr2' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zunmr2' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9250:5: Exception check on 'zunmr3' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zunmr3' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zunmr3' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9255:5: Exception check on 'zunmrq' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zunmrq' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zunmrq' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9260:5: Exception check on 'zunmrz' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zunmrz' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zunmrz' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9265:5: Exception check on 'zunmtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zunmtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zunmtr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9270:5: Exception check on 'zupgtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zupgtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zupgtr' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:9275:5: Exception check on 'zupmtr' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'zupmtr' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'zupmtr' to allow an error code to be returned.
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/work/scipy-1.2.3" && /opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 setup.py --no-user-cfg config_fc --fcompiler gnu95 --f77exec /opt/local/bin/gfortran-mp-13 --f77flags='-m64 -Os -fno-second-underscore -fallow-argument-mismatch' --f90exec /opt/local/bin/gfortran-mp-13 --f90flags='-m64 -Os -fno-second-underscore -fallow-argument-mismatch' config --cc /usr/bin/clang --include-dirs /opt/local/include --library-dirs /opt/local/lib build 
:info:build Exit code: 1
:error:build Failed to build py27-scipy: command execution failed
:debug:build Error code: CHILDSTATUS 7781 1
:debug:build Backtrace: command execution failed
:debug:build     while executing
:debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring"
:debug:build     invoked from within
:debug:build "command_exec -callback portprogress::target_progress_callback build"
:debug:build     (procedure "portbuild::build_main" line 10)
:debug:build     invoked from within
:debug:build "$procedure $targetname"
:error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py27-scipy/py27-scipy/main.log for details.