Ticket #69040: main.3.log

version:1
:debug:main Starting logging for py311-scipy @1.10.1_1+gfortran+openblas
:debug:sysinfo macOS 13.6.3 (darwin/22.6.0) arch i386
:debug:sysinfo MacPorts 2.8.1
:debug:sysinfo Xcode 15.1, CLT 15.1.0.0.1.1700200546
:debug:sysinfo SDK 13
:debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 13.0
:msg:main --->  Computing dependencies for py311-scipy:info:main .:debug:main py311-scipy has no conflicts
:debug:main Searching for dependency: py311-pythran
:debug:main Found Dependency: receipt exists for py311-pythran
:debug:main Searching for dependency: swig-python
:debug:main Found Dependency: receipt exists for swig-python
:debug:main Searching for dependency: gcc13
:debug:main Found Dependency: receipt exists for gcc13
:debug:main Searching for dependency: py311-numpy
:debug:main Found Dependency: receipt exists for py311-numpy
:debug:main Searching for dependency: py311-pybind11
:debug:main Found Dependency: receipt exists for py311-pybind11
:debug:main Searching for dependency: py311-mypy
:debug:main Found Dependency: receipt exists for py311-mypy
:debug:main Searching for dependency: libgcc
:debug:main Found Dependency: receipt exists for libgcc
:debug:main Searching for dependency: OpenBLAS
:debug:main Found Dependency: receipt exists for OpenBLAS
:debug:main Searching for dependency: python311
:debug:main Found Dependency: receipt exists for python311
:debug:main Searching for dependency: boost176
:debug:main Found Dependency: receipt exists for boost176
:debug:main Executing org.macports.main (py311-scipy)
:debug:main Privilege de-escalation not attempted as not running as root.
:debug:archivefetch archivefetch phase started at Fri Jan  5 12:36:59 EST 2024
:debug:archivefetch Executing proc-pre-org.macports.archivefetch-archivefetch-0
:debug:archivefetch Executing org.macports.archivefetch (py311-scipy)
:debug:archivefetch Privilege de-escalation not attempted as not running as root.
:debug:archivefetch Skipping completed org.macports.fetch (py311-scipy)
:debug:archivefetch Privilege de-escalation not attempted as not running as root.
:debug:archivefetch Skipping completed org.macports.checksum (py311-scipy)
:debug:archivefetch Privilege de-escalation not attempted as not running as root.
:debug:archivefetch Skipping completed org.macports.extract (py311-scipy)
:debug:archivefetch Privilege de-escalation not attempted as not running as root.
:debug:archivefetch Skipping completed org.macports.patch (py311-scipy)
:debug:archivefetch Privilege de-escalation not attempted as not running as root.
:debug:archivefetch Skipping completed org.macports.configure (py311-scipy)
:debug:archivefetch Privilege de-escalation not attempted as not running as root.
:debug:build build phase started at Fri Jan  5 12:36:59 EST 2024
:notice:build --->  Building py311-scipy
:debug:build Executing proc-pre-org.macports.build-build-0
:debug:build Executing org.macports.build (py311-scipy)
:debug:build Environment: 
:debug:build ATLAS='None'
:debug:build BOOSTDIR='/Users/sbasu1/packages/macports/libexec/boost/1.76'
:debug:build BOOSTROOT='/Users/sbasu1/packages/macports/libexec/boost/1.76'
:debug:build BOOST_DIR='/Users/sbasu1/packages/macports/libexec/boost/1.76'
:debug:build BOOST_INCLUDEDIR='/Users/sbasu1/packages/macports/libexec/boost/1.76/include'
:debug:build BOOST_LIBRARYDIR='/Users/sbasu1/packages/macports/libexec/boost/1.76/lib'
:debug:build BOOST_ROOT='/Users/sbasu1/packages/macports/libexec/boost/1.76'
:debug:build CC='/usr/bin/clang'
:debug:build CCFLAGS='-I/Users/sbasu1/packages/macports/include -L/Users/sbasu1/packages/macports/lib'
:debug:build CC_PRINT_OPTIONS='YES'
:debug:build CC_PRINT_OPTIONS_FILE='/Users/sbasu1/packages/macports/var/macports/build/_Users_sbasu1_packages_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-scipy/py311-scipy/work/.CC_PRINT_OPTIONS'
:debug:build CFLAGS='-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk'
:debug:build CPATH='/Users/sbasu1/packages/macports/libexec/boost/1.76/include:/Users/sbasu1/packages/macports/include'
:debug:build CXX='/usr/bin/clang++'
:debug:build CXXFLAGS='-stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk'
:debug:build DEVELOPER_DIR='/Library/Developer/CommandLineTools'
:debug:build F77='/Users/sbasu1/packages/macports/bin/gfortran-mp-13'
:debug:build F90='/Users/sbasu1/packages/macports/bin/gfortran-mp-13'
:debug:build FC='/Users/sbasu1/packages/macports/bin/gfortran-mp-13'
:debug:build LIBRARY_PATH='/Users/sbasu1/packages/macports/lib'
:debug:build MACOSX_DEPLOYMENT_TARGET='13.0'
:debug:build MACPORTS_LEGACY_SUPPORT_DISABLED='1'
:debug:build MKLROOT='None'
:debug:build OBJC='/usr/bin/clang'
:debug:build OBJCFLAGS='-isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk'
:debug:build OPENBLAS='/Users/sbasu1/packages/macports/lib'
:debug:build SDKROOT='/Library/Developer/CommandLineTools/SDKs/MacOSX13.sdk'
:debug:build SETUPTOOLS_USE_DISTUTILS='stdlib'
:info:build Executing:  cd "/Users/sbasu1/packages/macports/var/macports/build/_Users_sbasu1_packages_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-scipy/py311-scipy/work/scipy-1.10.1" && /Users/sbasu1/packages/macports/Library/Frameworks/Python.framework/Versions/3.11/bin/python3.11 setup.py --no-user-cfg build -j4 
:debug:build system:  cd "/Users/sbasu1/packages/macports/var/macports/build/_Users_sbasu1_packages_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-scipy/py311-scipy/work/scipy-1.10.1" && /Users/sbasu1/packages/macports/Library/Frameworks/Python.framework/Versions/3.11/bin/python3.11 setup.py --no-user-cfg build -j4 
:info:build /Users/sbasu1/packages/macports/var/macports/build/_Users_sbasu1_packages_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-scipy/py311-scipy/work/scipy-1.10.1/setup.py:124: DeprecationWarning: The distutils package is deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 632 for potential alternatives
:info:build   from distutils.command.sdist import sdist
:info:build /Users/sbasu1/packages/macports/var/macports/build/_Users_sbasu1_packages_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-scipy/py311-scipy/work/scipy-1.10.1/setup.py:507: DeprecationWarning: 
:info:build   `numpy.distutils` is deprecated since NumPy 1.23.0, as a result
:info:build   of the deprecation of `distutils` itself. It will be removed for
:info:build   Python >= 3.12. For older Python versions it will remain present.
:info:build   It is recommended to use `setuptools < 60.0` for those Python versions.
:info:build   For more details, see:
:info:build     https://numpy.org/devdocs/reference/distutils_status_migration.html 
:info:build   from numpy.distutils.core import setup
:info:build Running from SciPy source directory.
:info:build scipy/linalg/_generate_pyx.py: all files up-to-date
:info:build scipy/special/_generate_pyx.py: all files up-to-date
:info:build Running scipy/linalg/_generate_pyx.py
:info:build Running scipy/special/_generate_pyx.py
:info:build Running scipy/stats/_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/_matfuncs_sqrtm_triu.pyx
:info:build Processing scipy/linalg/_cythonized_array_utils.pyx
:info:build Processing scipy/linalg/_matfuncs_expm.pyx.in
:info:build Processing scipy/linalg/_solve_toeplitz.pyx
:info:build Processing scipy/linalg/cython_blas.pyx
:info:build Processing scipy/linalg/_decomp_update.pyx.in
:info:build Processing scipy/optimize/_group_columns.pyx
:info:build Processing scipy/optimize/_bglu_dense.pyx
:info:build Processing scipy/optimize/_trlib/_trlib.pyx
:info:build Processing scipy/optimize/_highs/cython/src/_highs_constants.pyx
:info:build warning: cython_blas.pyx:1029: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 Processing scipy/optimize/_highs/cython/src/_highs_wrapper.pyx
:info:build performance hint: _ni_label.pyx:54: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:66: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 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:45:62: Cannot assign type 'void (object) except *' to 'PyCapsule_Destructor'. Exception values are incompatible. Suggest adding 'noexcept' to type 'void (object) except *'.
:info:build Traceback (most recent call last):
:info:build   File "/Users/sbasu1/packages/macports/var/macports/build/_Users_sbasu1_packages_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-scipy/py311-scipy/work/scipy-1.10.1/tools/cythonize.py", line 317, in <module>
:info:build     main()
:info:build   File "/Users/sbasu1/packages/macports/var/macports/build/_Users_sbasu1_packages_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-scipy/py311-scipy/work/scipy-1.10.1/tools/cythonize.py", line 313, in main
:info:build     find_process_files(root_dir)
:info:build   File "/Users/sbasu1/packages/macports/var/macports/build/_Users_sbasu1_packages_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-scipy/py311-scipy/work/scipy-1.10.1/tools/cythonize.py", line 302, in find_process_files
:info:build     for result in pool.imap_unordered(lambda args: process(*args), jobs):
:info:build   File "/Users/sbasu1/packages/macports/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/multiprocessing/pool.py", line 873, in next
:info:build     raise value
:info:build   File "/Users/sbasu1/packages/macports/Library/Frameworks/Python.framework/Versions/3.11/lib/python3.11/multiprocessing/pool.py", line 125, in worker
:info:build     result = (True, func(*args, **kwds))
:info:build                     ^^^^^^^^^^^^^^^^^^^
:info:build   File "/Users/sbasu1/packages/macports/var/macports/build/_Users_sbasu1_packages_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-scipy/py311-scipy/work/scipy-1.10.1/tools/cythonize.py", line 302, in <lambda>
:info:build     for result in pool.imap_unordered(lambda args: process(*args), jobs):
:info:build                                                    ^^^^^^^^^^^^^^
:info:build   File "/Users/sbasu1/packages/macports/var/macports/build/_Users_sbasu1_packages_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-scipy/py311-scipy/work/scipy-1.10.1/tools/cythonize.py", line 236, in process
:info:build Processing scipy/optimize/_lsq/givens_elimination.pyx
:info:build     processor_function(fromfile, tofile, cwd=path)
:info:build   File "/Users/sbasu1/packages/macports/var/macports/build/_Users_sbasu1_packages_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-scipy/py311-scipy/work/scipy-1.10.1/tools/cythonize.py", line 102, in process_pyx
:info:build     raise Exception('Cython failed')
:info:build Exception: Cython failed
:info:build performance hint: _cythonized_array_utils.pyx:18:5: Exception check on 'swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _cythonized_array_utils.pyx:132:5: Exception check on 'band_check_internal_c' will always require the GIL to be acquired. Declare 'band_check_internal_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:163:5: Exception check on 'band_check_internal_noncontig' will always require the GIL to be acquired. Declare 'band_check_internal_noncontig' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build Cythonizing sources
:info:build Traceback (most recent call last):
:info:build   File "/Users/sbasu1/packages/macports/var/macports/build/_Users_sbasu1_packages_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-scipy/py311-scipy/work/scipy-1.10.1/setup.py", line 533, in <module>
:info:build     setup_package()
:info:build   File "/Users/sbasu1/packages/macports/var/macports/build/_Users_sbasu1_packages_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-scipy/py311-scipy/work/scipy-1.10.1/setup.py", line 517, in setup_package
:info:build     generate_cython()
:info:build   File "/Users/sbasu1/packages/macports/var/macports/build/_Users_sbasu1_packages_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-scipy/py311-scipy/work/scipy-1.10.1/setup.py", line 266, in generate_cython
:info:build     raise RuntimeError("Running cythonize failed!")
:info:build RuntimeError: Running cythonize failed!
:info:build Error compiling Cython file:
:info:build ------------------------------------------------------------
:info:build ...
:info:build from .linalg cimport cython_blas, cython_lapack
:info:build ^
:info:build ------------------------------------------------------------
:info:build /Users/sbasu1/packages/macports/var/macports/build/_Users_sbasu1_packages_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-scipy/py311-scipy/work/scipy-1.10.1/scipy/linalg.pxd:1:0: 'scipy/linalg/linalg.pxd' not found
:info:build performance hint: cython_blas.pyx:192: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:200: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.pyx:352: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:360: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:367: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:372: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:377: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:382: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:387: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:392: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:397: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:402: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:407: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:412: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:417: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:422: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:427: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:432: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:437: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:442: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:447: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:452: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:457: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:462: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:467: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:472: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:477: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:482: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:487: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:492: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:497: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:502: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:507: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:512: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:517: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:522: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:527: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:532: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:537: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:542: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:547: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:552: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:557: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:562: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:567: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:572: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:577: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:582: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:587: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:592: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:597: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:602: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:607: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:612: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:617: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:622: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:627: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:632: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:637: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:642: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:647: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:652: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:657: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:662: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:667: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:672: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:677: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:682: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:687: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:692: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:697: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:702: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:707: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:712: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:717: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:722: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:727: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:732: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:737: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:742: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:747: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:752: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:757: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:762: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:767: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 performance hint: cython_blas.pyx:772: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 performance hint: cython_blas.pyx:777: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 performance hint: cython_blas.pyx:782: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:787: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:792: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:797: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:802: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:807: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:812: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:817: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:822: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:827: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:832: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:837: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:842: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:847: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:852: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:857: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:862: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:867: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:872: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:877: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:882: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:887: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:892: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:897: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:902: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:907: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:912: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:917: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:922: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:927: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:932: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:937: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:942: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:947: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:952: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:957: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:962: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:967: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:972: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:977: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:982: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:987: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:992: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 performance hint: cython_blas.pyx:1001: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:1008: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:1180: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:1187: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: _ni_label.pyx:321:28: Exception check after calling 'nonzero_line' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '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 'nonzero_line' to allow an error code to be returned.
:info:build performance hint: _ni_label.pyx:355:37: Exception check after calling 'read_line' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '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 'read_line' to allow an error code to be returned.
:info:build performance hint: _ni_label.pyx:398:39: Exception check after calling 'write_line' will always require the GIL to be acquired. Declare 'write_line' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _ni_label.pyx:430:25: Exception check after calling 'read_line' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '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 'read_line' to allow an error code to be returned.
:info:build performance hint: _ni_label.pyx:433:26: Exception check after calling 'write_line' will always require the GIL to be acquired. Declare 'write_line' 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:1006:16: Exception check after calling '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:1013:16: Exception check after calling '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.pyx:1069: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:1100: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:1185:16: Exception check after calling '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:1192:16: Exception check after calling '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: _cythonized_array_utils.pyx:36:31: Exception check after calling '__pyx_fuse_0swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_0swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_0swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _cythonized_array_utils.pyx:37:31: Exception check after calling '__pyx_fuse_0swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_0swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_0swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _cythonized_array_utils.pyx:40:31: Exception check after calling '__pyx_fuse_0swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_0swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_0swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _cythonized_array_utils.pyx:41:31: Exception check after calling '__pyx_fuse_0swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_0swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_0swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _cythonized_array_utils.pyx:36:31: Exception check after calling '__pyx_fuse_1swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_1swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_1swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _cythonized_array_utils.pyx:37:31: Exception check after calling '__pyx_fuse_1swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_1swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_1swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _cythonized_array_utils.pyx:40:31: Exception check after calling '__pyx_fuse_1swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_1swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_1swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _cythonized_array_utils.pyx:41:31: Exception check after calling '__pyx_fuse_1swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_1swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_1swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _cythonized_array_utils.pyx:36:31: Exception check after calling '__pyx_fuse_2swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_2swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_2swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _cythonized_array_utils.pyx:37:31: Exception check after calling '__pyx_fuse_2swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_2swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_2swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _cythonized_array_utils.pyx:40:31: Exception check after calling '__pyx_fuse_2swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_2swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_2swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _cythonized_array_utils.pyx:41:31: Exception check after calling '__pyx_fuse_2swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_2swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_2swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _cythonized_array_utils.pyx:36:31: Exception check after calling '__pyx_fuse_3swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_3swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_3swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _cythonized_array_utils.pyx:37:31: Exception check after calling '__pyx_fuse_3swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_3swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_3swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _cythonized_array_utils.pyx:40:31: Exception check after calling '__pyx_fuse_3swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_3swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_3swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _cythonized_array_utils.pyx:41:31: Exception check after calling '__pyx_fuse_3swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_3swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_3swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _cythonized_array_utils.pyx:117:36: Exception check after calling '__pyx_fuse_0band_check_internal_c' will always require the GIL to be acquired. Declare '__pyx_fuse_0band_check_internal_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:117:36: Exception check after calling '__pyx_fuse_1band_check_internal_c' will always require the GIL to be acquired. Declare '__pyx_fuse_1band_check_internal_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:117:36: Exception check after calling '__pyx_fuse_2band_check_internal_c' will always require the GIL to be acquired. Declare '__pyx_fuse_2band_check_internal_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:117:36: Exception check after calling '__pyx_fuse_3band_check_internal_c' will always require the GIL to be acquired. Declare '__pyx_fuse_3band_check_internal_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:117:36: Exception check after calling '__pyx_fuse_4band_check_internal_c' will always require the GIL to be acquired. Declare '__pyx_fuse_4band_check_internal_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:117:36: Exception check after calling '__pyx_fuse_5band_check_internal_c' will always require the GIL to be acquired. Declare '__pyx_fuse_5band_check_internal_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:117:36: Exception check after calling '__pyx_fuse_6band_check_internal_c' will always require the GIL to be acquired. Declare '__pyx_fuse_6band_check_internal_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:117:36: Exception check after calling '__pyx_fuse_7band_check_internal_c' will always require the GIL to be acquired. Declare '__pyx_fuse_7band_check_internal_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:117:36: Exception check after calling '__pyx_fuse_8band_check_internal_c' will always require the GIL to be acquired. Declare '__pyx_fuse_8band_check_internal_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:117:36: Exception check after calling '__pyx_fuse_9band_check_internal_c' will always require the GIL to be acquired. Declare '__pyx_fuse_9band_check_internal_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:117:36: Exception check after calling '__pyx_fuse_10band_check_internal_c' will always require the GIL to be acquired. Declare '__pyx_fuse_10band_check_internal_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:117:36: Exception check after calling '__pyx_fuse_11band_check_internal_c' will always require the GIL to be acquired. Declare '__pyx_fuse_11band_check_internal_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:117:36: Exception check after calling '__pyx_fuse_12band_check_internal_c' will always require the GIL to be acquired. Declare '__pyx_fuse_12band_check_internal_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:125:44: Exception check after calling '__pyx_fuse_0band_check_internal_noncontig' will always require the GIL to be acquired. Declare '__pyx_fuse_0band_check_internal_noncontig' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:125:44: Exception check after calling '__pyx_fuse_1band_check_internal_noncontig' will always require the GIL to be acquired. Declare '__pyx_fuse_1band_check_internal_noncontig' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:125:44: Exception check after calling '__pyx_fuse_2band_check_internal_noncontig' will always require the GIL to be acquired. Declare '__pyx_fuse_2band_check_internal_noncontig' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:125:44: Exception check after calling '__pyx_fuse_3band_check_internal_noncontig' will always require the GIL to be acquired. Declare '__pyx_fuse_3band_check_internal_noncontig' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:125:44: Exception check after calling '__pyx_fuse_4band_check_internal_noncontig' will always require the GIL to be acquired. Declare '__pyx_fuse_4band_check_internal_noncontig' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:125:44: Exception check after calling '__pyx_fuse_5band_check_internal_noncontig' will always require the GIL to be acquired. Declare '__pyx_fuse_5band_check_internal_noncontig' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:125:44: Exception check after calling '__pyx_fuse_6band_check_internal_noncontig' will always require the GIL to be acquired. Declare '__pyx_fuse_6band_check_internal_noncontig' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:125:44: Exception check after calling '__pyx_fuse_7band_check_internal_noncontig' will always require the GIL to be acquired. Declare '__pyx_fuse_7band_check_internal_noncontig' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:125:44: Exception check after calling '__pyx_fuse_8band_check_internal_noncontig' will always require the GIL to be acquired. Declare '__pyx_fuse_8band_check_internal_noncontig' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:125:44: Exception check after calling '__pyx_fuse_9band_check_internal_noncontig' will always require the GIL to be acquired. Declare '__pyx_fuse_9band_check_internal_noncontig' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:125:44: Exception check after calling '__pyx_fuse_10band_check_internal_noncontig' will always require the GIL to be acquired. Declare '__pyx_fuse_10band_check_internal_noncontig' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:125:44: Exception check after calling '__pyx_fuse_11band_check_internal_noncontig' will always require the GIL to be acquired. Declare '__pyx_fuse_11band_check_internal_noncontig' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _cythonized_array_utils.pyx:125:44: Exception check after calling '__pyx_fuse_12band_check_internal_noncontig' will always require the GIL to be acquired. Declare '__pyx_fuse_12band_check_internal_noncontig' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build performance hint: _matfuncs_expm.pyx:547:5: Exception check on 'pade_357_UV_calc_s' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'pade_357_UV_calc_s' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'pade_357_UV_calc_s' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:640:5: Exception check on 'pade_357_UV_calc_d' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'pade_357_UV_calc_d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'pade_357_UV_calc_d' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:733:5: Exception check on 'pade_357_UV_calc_c' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'pade_357_UV_calc_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'pade_357_UV_calc_c' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:826:5: Exception check on 'pade_357_UV_calc_z' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'pade_357_UV_calc_z' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'pade_357_UV_calc_z' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:919:5: Exception check on 'pade_9_UV_calc_s' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'pade_9_UV_calc_s' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'pade_9_UV_calc_s' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:981:5: Exception check on 'pade_9_UV_calc_d' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'pade_9_UV_calc_d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'pade_9_UV_calc_d' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:1043:5: Exception check on 'pade_9_UV_calc_c' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'pade_9_UV_calc_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'pade_9_UV_calc_c' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:1105:5: Exception check on 'pade_9_UV_calc_z' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'pade_9_UV_calc_z' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'pade_9_UV_calc_z' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:1167:5: Exception check on 'pade_13_UV_calc_s' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'pade_13_UV_calc_s' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'pade_13_UV_calc_s' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:1251:5: Exception check on 'pade_13_UV_calc_d' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'pade_13_UV_calc_d' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'pade_13_UV_calc_d' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:1335:5: Exception check on 'pade_13_UV_calc_c' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'pade_13_UV_calc_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'pade_13_UV_calc_c' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:1419:5: Exception check on 'pade_13_UV_calc_z' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare 'pade_13_UV_calc_z' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on 'pade_13_UV_calc_z' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:581:17: Exception check after calling '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: _matfuncs_expm.pyx:582:17: Exception check after calling '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: _matfuncs_expm.pyx:584:17: Exception check after calling '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: _matfuncs_expm.pyx:590:17: Exception check after calling '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: _matfuncs_expm.pyx:591:17: Exception check after calling '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: _matfuncs_expm.pyx:592:17: Exception check after calling '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: _matfuncs_expm.pyx:595:17: Exception check after calling '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: _matfuncs_expm.pyx:597:17: Exception check after calling '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: _matfuncs_expm.pyx:598:17: Exception check after calling '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: _matfuncs_expm.pyx:604:17: Exception check after calling '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: _matfuncs_expm.pyx:605:17: Exception check after calling '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: _matfuncs_expm.pyx:606:17: Exception check after calling '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: _matfuncs_expm.pyx:607:17: Exception check after calling '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: _matfuncs_expm.pyx:612:17: Exception check after calling '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: _matfuncs_expm.pyx:613:17: Exception check after calling '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: _matfuncs_expm.pyx:614:17: Exception check after calling '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: _matfuncs_expm.pyx:618:17: Exception check after calling '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: _matfuncs_expm.pyx:621:13: Exception check after calling '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: _matfuncs_expm.pyx:624:27: Exception check after calling '__pyx_fuse_0swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_0swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_0swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:626:14: Exception check after calling '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: _matfuncs_expm.pyx:627:14: Exception check after calling '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: _matfuncs_expm.pyx:628:13: Exception check after calling '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: _matfuncs_expm.pyx:633:27: Exception check after calling '__pyx_fuse_0swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_0swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_0swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:674:17: Exception check after calling '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: _matfuncs_expm.pyx:675:17: 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: _matfuncs_expm.pyx:677:17: Exception check after calling '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: _matfuncs_expm.pyx:683:17: Exception check after calling '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: _matfuncs_expm.pyx:684:17: Exception check after calling '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: _matfuncs_expm.pyx:685:17: Exception check after calling '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: _matfuncs_expm.pyx:688:17: 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: _matfuncs_expm.pyx:690:17: Exception check after calling '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: _matfuncs_expm.pyx:691:17: Exception check after calling '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: _matfuncs_expm.pyx:697:17: Exception check after calling '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: _matfuncs_expm.pyx:698:17: Exception check after calling '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: _matfuncs_expm.pyx:699:17: Exception check after calling '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: _matfuncs_expm.pyx:700:17: Exception check after calling '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: _matfuncs_expm.pyx:705:17: Exception check after calling '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: _matfuncs_expm.pyx:706:17: Exception check after calling '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: _matfuncs_expm.pyx:707:17: Exception check after calling '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: _matfuncs_expm.pyx:711:17: 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: _matfuncs_expm.pyx:714:13: Exception check after calling '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: _matfuncs_expm.pyx:717:27: Exception check after calling '__pyx_fuse_1swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_1swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_1swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:719:14: Exception check after calling '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: _matfuncs_expm.pyx:720:14: Exception check after calling '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: _matfuncs_expm.pyx:721:13: Exception check after calling '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: _matfuncs_expm.pyx:726:27: Exception check after calling '__pyx_fuse_1swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_1swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_1swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:767:17: Exception check after calling '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: _matfuncs_expm.pyx:768:17: Exception check after calling '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: _matfuncs_expm.pyx:770:17: Exception check after calling '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: _matfuncs_expm.pyx:776:17: Exception check after calling '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: _matfuncs_expm.pyx:777:17: Exception check after calling '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: _matfuncs_expm.pyx:778:17: Exception check after calling '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: _matfuncs_expm.pyx:781:17: Exception check after calling '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: _matfuncs_expm.pyx:783:17: Exception check after calling '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: _matfuncs_expm.pyx:784:17: Exception check after calling '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: _matfuncs_expm.pyx:790:17: Exception check after calling '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: _matfuncs_expm.pyx:791:17: Exception check after calling '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: _matfuncs_expm.pyx:792:17: Exception check after calling '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: _matfuncs_expm.pyx:793:17: Exception check after calling '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: _matfuncs_expm.pyx:798:17: Exception check after calling '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: _matfuncs_expm.pyx:799:17: Exception check after calling '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: _matfuncs_expm.pyx:800:17: Exception check after calling '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: _matfuncs_expm.pyx:804:17: Exception check after calling '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: _matfuncs_expm.pyx:807:13: Exception check after calling '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: _matfuncs_expm.pyx:810:27: Exception check after calling '__pyx_fuse_2swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_2swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_2swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:812:14: Exception check after calling '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: _matfuncs_expm.pyx:813:14: Exception check after calling '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: _matfuncs_expm.pyx:814:14: Exception check after calling '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: _matfuncs_expm.pyx:819:27: Exception check after calling '__pyx_fuse_2swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_2swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_2swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:860:17: Exception check after calling '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: _matfuncs_expm.pyx:861:17: Exception check after calling '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: _matfuncs_expm.pyx:863:17: Exception check after calling '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: _matfuncs_expm.pyx:869:17: Exception check after calling '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: _matfuncs_expm.pyx:870:17: Exception check after calling '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: _matfuncs_expm.pyx:871:17: Exception check after calling '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: _matfuncs_expm.pyx:874:17: Exception check after calling '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: _matfuncs_expm.pyx:876:17: Exception check after calling '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: _matfuncs_expm.pyx:877:17: Exception check after calling '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: _matfuncs_expm.pyx:883:17: Exception check after calling '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: _matfuncs_expm.pyx:884:17: Exception check after calling '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: _matfuncs_expm.pyx:885:17: Exception check after calling '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: _matfuncs_expm.pyx:886:17: Exception check after calling '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: _matfuncs_expm.pyx:891:17: Exception check after calling '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: _matfuncs_expm.pyx:892:17: Exception check after calling '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: _matfuncs_expm.pyx:893:17: Exception check after calling '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: _matfuncs_expm.pyx:897:17: Exception check after calling '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: _matfuncs_expm.pyx:900:13: Exception check after calling '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: _matfuncs_expm.pyx:903:27: Exception check after calling '__pyx_fuse_3swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_3swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_3swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:905:14: Exception check after calling '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: _matfuncs_expm.pyx:906:14: Exception check after calling '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: _matfuncs_expm.pyx:907:14: Exception check after calling '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: _matfuncs_expm.pyx:912:27: Exception check after calling '__pyx_fuse_3swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_3swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_3swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:943:13: Exception check after calling '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: _matfuncs_expm.pyx:944:13: Exception check after calling '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: _matfuncs_expm.pyx:945:13: Exception check after calling '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: _matfuncs_expm.pyx:946:13: Exception check after calling '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: _matfuncs_expm.pyx:947:13: Exception check after calling '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: _matfuncs_expm.pyx:951:13: Exception check after calling '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: _matfuncs_expm.pyx:952:13: Exception check after calling '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: _matfuncs_expm.pyx:953:13: Exception check after calling '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: _matfuncs_expm.pyx:954:13: Exception check after calling '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: _matfuncs_expm.pyx:958:13: Exception check after calling '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: _matfuncs_expm.pyx:961:13: Exception check after calling '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: _matfuncs_expm.pyx:964:27: Exception check after calling '__pyx_fuse_0swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_0swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_0swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:966:14: Exception check after calling '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: _matfuncs_expm.pyx:967:14: Exception check after calling '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: _matfuncs_expm.pyx:968:13: Exception check after calling '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: _matfuncs_expm.pyx:973:27: Exception check after calling '__pyx_fuse_0swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_0swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_0swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:1005:13: Exception check after calling '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: _matfuncs_expm.pyx:1006:13: Exception check after calling '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: _matfuncs_expm.pyx:1007:13: Exception check after calling '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: _matfuncs_expm.pyx:1008:13: Exception check after calling '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: _matfuncs_expm.pyx:1009:13: Exception check after calling '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: _matfuncs_expm.pyx:1013:13: Exception check after calling '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: _matfuncs_expm.pyx:1014:13: Exception check after calling '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: _matfuncs_expm.pyx:1015:13: Exception check after calling '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: _matfuncs_expm.pyx:1016:13: Exception check after calling '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: _matfuncs_expm.pyx:1020: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: _matfuncs_expm.pyx:1023:13: Exception check after calling '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: _matfuncs_expm.pyx:1026:27: Exception check after calling '__pyx_fuse_1swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_1swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_1swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:1028:14: Exception check after calling '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: _matfuncs_expm.pyx:1029:14: Exception check after calling '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: _matfuncs_expm.pyx:1030:13: Exception check after calling '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: _matfuncs_expm.pyx:1035:27: Exception check after calling '__pyx_fuse_1swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_1swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_1swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:1067:13: Exception check after calling '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: _matfuncs_expm.pyx:1068:13: Exception check after calling '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: _matfuncs_expm.pyx:1069:13: Exception check after calling '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: _matfuncs_expm.pyx:1070:13: Exception check after calling '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: _matfuncs_expm.pyx:1071:13: Exception check after calling '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: _matfuncs_expm.pyx:1075:13: Exception check after calling '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: _matfuncs_expm.pyx:1076:13: Exception check after calling '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: _matfuncs_expm.pyx:1077:13: Exception check after calling '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: _matfuncs_expm.pyx:1078:13: Exception check after calling '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: _matfuncs_expm.pyx:1082:13: Exception check after calling '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: _matfuncs_expm.pyx:1085:13: Exception check after calling '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: _matfuncs_expm.pyx:1088:27: Exception check after calling '__pyx_fuse_2swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_2swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_2swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:1090:14: Exception check after calling '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: _matfuncs_expm.pyx:1091:14: Exception check after calling '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: _matfuncs_expm.pyx:1092:14: Exception check after calling '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: _matfuncs_expm.pyx:1097:27: Exception check after calling '__pyx_fuse_2swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_2swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_2swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:1129:13: Exception check after calling '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: _matfuncs_expm.pyx:1130:13: Exception check after calling '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: _matfuncs_expm.pyx:1131:13: Exception check after calling '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: _matfuncs_expm.pyx:1132:13: Exception check after calling '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: _matfuncs_expm.pyx:1133:13: Exception check after calling '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: _matfuncs_expm.pyx:1137:13: Exception check after calling '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: _matfuncs_expm.pyx:1138:13: Exception check after calling '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: _matfuncs_expm.pyx:1139:13: Exception check after calling '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: _matfuncs_expm.pyx:1140:13: Exception check after calling '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: _matfuncs_expm.pyx:1144:13: Exception check after calling '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: _matfuncs_expm.pyx:1147:13: Exception check after calling '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: _matfuncs_expm.pyx:1150:27: Exception check after calling '__pyx_fuse_3swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_3swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_3swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:1152:14: Exception check after calling '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: _matfuncs_expm.pyx:1153:14: Exception check after calling '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: _matfuncs_expm.pyx:1154:14: Exception check after calling '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: _matfuncs_expm.pyx:1159:27: Exception check after calling '__pyx_fuse_3swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_3swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_3swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:1200:13: Exception check after calling '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: _matfuncs_expm.pyx:1201:13: Exception check after calling '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: _matfuncs_expm.pyx:1202:13: Exception check after calling '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: _matfuncs_expm.pyx:1203:13: Exception check after calling '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: _matfuncs_expm.pyx:1205:13: Exception check after calling '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: _matfuncs_expm.pyx:1206:13: Exception check after calling '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: _matfuncs_expm.pyx:1207:13: Exception check after calling '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: _matfuncs_expm.pyx:1208:13: Exception check after calling '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: _matfuncs_expm.pyx:1210:13: Exception check after calling '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: _matfuncs_expm.pyx:1211:13: Exception check after calling '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: _matfuncs_expm.pyx:1212:13: Exception check after calling '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: _matfuncs_expm.pyx:1213:13: Exception check after calling '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: _matfuncs_expm.pyx:1216:13: Exception check after calling '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: _matfuncs_expm.pyx:1217:13: Exception check after calling '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: _matfuncs_expm.pyx:1218:13: Exception check after calling '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: _matfuncs_expm.pyx:1225:13: Exception check after calling '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: _matfuncs_expm.pyx:1226:13: Exception check after calling '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: _matfuncs_expm.pyx:1228:13: Exception check after calling '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: _matfuncs_expm.pyx:1230:13: Exception check after calling '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: _matfuncs_expm.pyx:1233:27: Exception check after calling '__pyx_fuse_0swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_0swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_0swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:1235:14: Exception check after calling '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: _matfuncs_expm.pyx:1236:14: Exception check after calling '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: _matfuncs_expm.pyx:1237:13: Exception check after calling '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: _matfuncs_expm.pyx:1241:27: Exception check after calling '__pyx_fuse_0swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_0swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_0swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:1561: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: _matfuncs_expm.pyx:1284:13: Exception check after calling '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: _matfuncs_expm.pyx:1285:13: Exception check after calling '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: _matfuncs_expm.pyx:1286:13: Exception check after calling '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: _matfuncs_expm.pyx:1287:13: Exception check after calling '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: _matfuncs_expm.pyx:1289:13: Exception check after calling '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: _matfuncs_expm.pyx:1290:13: Exception check after calling '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: _matfuncs_expm.pyx:1291:13: Exception check after calling '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: _matfuncs_expm.pyx:1292:13: Exception check after calling '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: _matfuncs_expm.pyx:1294:13: Exception check after calling '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: _matfuncs_expm.pyx:1295:13: Exception check after calling '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: _matfuncs_expm.pyx:1296:13: Exception check after calling '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: _matfuncs_expm.pyx:1297:13: Exception check after calling '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: _matfuncs_expm.pyx:1300:13: Exception check after calling '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: _matfuncs_expm.pyx:1301:13: Exception check after calling '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: _matfuncs_expm.pyx:1302:13: Exception check after calling '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: _matfuncs_expm.pyx:1309: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: _matfuncs_expm.pyx:1310: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: _matfuncs_expm.pyx:1312: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: _matfuncs_expm.pyx:1314:13: Exception check after calling '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: _matfuncs_expm.pyx:1317:27: Exception check after calling '__pyx_fuse_1swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_1swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_1swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:1319:14: Exception check after calling '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: _matfuncs_expm.pyx:1320:14: Exception check after calling '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: _matfuncs_expm.pyx:1321:13: Exception check after calling '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: _matfuncs_expm.pyx:1325:27: Exception check after calling '__pyx_fuse_1swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_1swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_1swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2081: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: _matfuncs_expm.pyx:1368:13: Exception check after calling '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: _matfuncs_expm.pyx:1369:13: Exception check after calling '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: _matfuncs_expm.pyx:1370:13: Exception check after calling '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: _matfuncs_expm.pyx:1371:13: Exception check after calling '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: _matfuncs_expm.pyx:1373:13: Exception check after calling '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: _matfuncs_expm.pyx:1374:13: Exception check after calling '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: _matfuncs_expm.pyx:1375:13: Exception check after calling '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: _matfuncs_expm.pyx:1376:13: Exception check after calling '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: _matfuncs_expm.pyx:1378:13: Exception check after calling '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_lapack.pyx:2208: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: _matfuncs_expm.pyx:1379:13: Exception check after calling '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: _matfuncs_expm.pyx:1380:13: Exception check after calling '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: _matfuncs_expm.pyx:1381:13: Exception check after calling '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_lapack.pyx:2213: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: _matfuncs_expm.pyx:1384:13: Exception check after calling '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: _matfuncs_expm.pyx:1385:13: Exception check after calling '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_lapack.pyx:2218: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: _matfuncs_expm.pyx:1386:13: Exception check after calling '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_lapack.pyx:2223: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: _matfuncs_expm.pyx:1393:13: Exception check after calling '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_lapack.pyx:2228: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: _matfuncs_expm.pyx:1394:13: Exception check after calling '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: _matfuncs_expm.pyx:1396:13: Exception check after calling '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: _matfuncs_expm.pyx:1398:13: Exception check after calling '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_lapack.pyx:2233: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: _matfuncs_expm.pyx:1401:27: Exception check after calling '__pyx_fuse_2swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_2swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_2swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:1403:14: Exception check after calling '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: _matfuncs_expm.pyx:1404:14: Exception check after calling '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: _matfuncs_expm.pyx:1405:14: Exception check after calling '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_lapack.pyx:2238: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: _matfuncs_expm.pyx:1409:27: Exception check after calling '__pyx_fuse_2swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_2swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_2swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2243: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:2248: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:2253: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:2258: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:2263: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:2268: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:2273: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:2278: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:2283: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:2288: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:2293: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:2298: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:2303: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:2308: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:2313: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:2318: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:2323: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:2328: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:2333: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:2338: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:2343: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:2348: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:2353: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:2358: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:2363: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:2368: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:2373: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: _matfuncs_expm.pyx:1452:13: Exception check after calling '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: _matfuncs_expm.pyx:1453:13: Exception check after calling '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_lapack.pyx:2378: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:2383: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: _matfuncs_expm.pyx:1454:13: Exception check after calling '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: _matfuncs_expm.pyx:1455:13: Exception check after calling '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_lapack.pyx:2388: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: _matfuncs_expm.pyx:1457:13: Exception check after calling '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_lapack.pyx:2393: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: _matfuncs_expm.pyx:1458:13: Exception check after calling '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: _matfuncs_expm.pyx:1459:13: Exception check after calling '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_lapack.pyx:2398: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: _matfuncs_expm.pyx:1460:13: Exception check after calling '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_lapack.pyx:2403: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: _matfuncs_expm.pyx:1462:13: Exception check after calling '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: _matfuncs_expm.pyx:1463:13: Exception check after calling '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_lapack.pyx:2408: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: _matfuncs_expm.pyx:1464:13: Exception check after calling '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_lapack.pyx:2413: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: _matfuncs_expm.pyx:1465:13: Exception check after calling '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: _matfuncs_expm.pyx:1468:13: Exception check after calling '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: _matfuncs_expm.pyx:1469:13: Exception check after calling '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_lapack.pyx:2418: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: _matfuncs_expm.pyx:1470:13: Exception check after calling '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_lapack.pyx:2423: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: _matfuncs_expm.pyx:1477:13: Exception check after calling '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_lapack.pyx:2428: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:2433: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: _matfuncs_expm.pyx:1478:13: Exception check after calling '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: _matfuncs_expm.pyx:1480:13: Exception check after calling '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: _matfuncs_expm.pyx:1482:13: Exception check after calling '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_lapack.pyx:2438: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: _matfuncs_expm.pyx:1485:27: Exception check after calling '__pyx_fuse_3swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_3swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_3swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: _matfuncs_expm.pyx:1487:14: Exception check after calling '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:2443: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: _matfuncs_expm.pyx:1488:14: Exception check after calling '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: _matfuncs_expm.pyx:1489:14: Exception check after calling '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_lapack.pyx:2448: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: _matfuncs_expm.pyx:1493:27: Exception check after calling '__pyx_fuse_3swap_c_and_f_layout' will always require the GIL to be acquired.
:info:build Possible solutions:
:info:build     1. Declare '__pyx_fuse_3swap_c_and_f_layout' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
:info:build     2. Use an 'int' return type on '__pyx_fuse_3swap_c_and_f_layout' to allow an error code to be returned.
:info:build performance hint: cython_lapack.pyx:2453: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:2458: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:2463: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:2468: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:2473: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:2478: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:2483: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:2488: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:2493: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:2498: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:2503: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:2508: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:2513: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:2518: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:2523: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:2528: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:2533: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:2538: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:2543: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:2548: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:2553: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:2558: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:2563: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:2568: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:2573: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:2578: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:2583: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:2588: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:2593: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:2598: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:2603: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:2608: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:2613: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:2618: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:2623: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:2628: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:2633: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:2638: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:2643: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:2648: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:2653: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:2658: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:2663: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:2668: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:2673: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:2678: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:2683: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:2688: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:2693: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:2698: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:2703: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:2708: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:2713: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:2718: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:2723: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:2728: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:2733: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:2738: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:2743: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:2748: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:2753: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:2758: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:2763: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:2768: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:2773: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:2778: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:2783: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:2788: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:2793: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:2798: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:2803: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:2808: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:2813: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:2818: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:2823: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:2828: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:2833: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:2838: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:2843: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:2848: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:2853: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:2858: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:2863: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:2868: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:2873: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:2878: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:2883: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:2888: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:2893: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:2898: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:2903: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:2908: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:2913: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:2918: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:2923: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:2928: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:2933: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:2938: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:2943: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:2948: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:2953: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:2958: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:2963: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:2968: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:2973: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:2978: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:2983: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:2988: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:2993: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:2998: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:3003: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:3008: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:3013: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:3018: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:3023: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:3028: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:3033: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:3038: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:3043: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:3048: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:3053: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:3058: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:3063: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:3068: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:3073: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:3078: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:3083: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:3088: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:3093: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:3098: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:3103: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:3108: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:3113: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:3118: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:3123: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:3128: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:3133: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:3138: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:3143: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:3148: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:3153: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:3158: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:3163: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:3168: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:3173: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:3178: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:3183: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:3188: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:3193: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:3198: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:3203: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:3208: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:3213: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:3218: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:3223: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:3228: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:3233: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:3238: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:3243: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:3248: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:3253: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:3258: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:3263: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:3268: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:3273: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:3278: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:3283: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:3288: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:3293: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:3298: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:3303: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:3308: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:3313: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:3318: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:3323: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:3328: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:3333: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:3338: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:3343: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:3348: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:3353: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:3358: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:3363: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:3368: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:3373: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:3378: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:3383: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:3388: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:3393: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:3398: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:3403: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:3408: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:3413: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:3418: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:3423: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:3428: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:3433: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:3438: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:3443: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:3448: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:3453: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:3458: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:3463: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:3468: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:3473: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:3478: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:3483: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:3488: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:3493: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:3498: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:3503: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:3508: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:3513: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:3518: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:3523: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:3528: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:3533: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:3538: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:3543: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:3548: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:3553: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:3558: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:3563: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:3568: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:3573: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:3578: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:3583: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:3588: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:3593: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:3598: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:3603: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:3608: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:3613: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:3618: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:3623: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:3628: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:3633: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:3638: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:3643: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:3648: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:3653: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:3658: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:3663: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:3668: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:3673: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:3678: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:3683: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:3688: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:3693: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:3698: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:3703: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:3708: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:3713: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:3718: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:3723: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:3728: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:3733: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:3738: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:3743: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:3748: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:3753: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:3758: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:3763: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:3768: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:3773: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:3778: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:3783: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:3788: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:3793: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:3798: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:3803: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:3808: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:3813: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:3818: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:3823: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:3828: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:3833: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:3838: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:3843: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:3848: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:3853: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:3858: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:3863: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:3868: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:3873: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:3878: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:3883: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:3888: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:3893: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:3898: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:3903: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:3908: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:3913: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:3918: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:3923: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:3928: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:3933: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:3938: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:3943: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:3948: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:3953: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:3958: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:3963: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:3968: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:3973: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:3978: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:3983: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:3988: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:3993: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:3998: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:4003: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:4008: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:4013: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:4018: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:4023: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:4028: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:4033: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:4038: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:4043: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:4048: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:4053: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:4058: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:4063: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:4068: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:4073: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:4078: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:4083: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:4088: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:4093: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:4098: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:4103: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:4108: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:4113: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:4118: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:4123: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:4128: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:4133: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:4138: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:4143: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:4148: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:4153: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:4158: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:4163: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:4168: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:4173: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:4178: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:4183: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:4188: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:4193: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:4198: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:4203: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:4208: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:4213: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:4218: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:4223: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:4228: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:4233: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:4238: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:4243: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:4248: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:4253: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:4258: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:4263: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:4268: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:4273: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:4278: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:4283: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:4288: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:4293: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:4298: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:4303: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:4308: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:4313: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:4318: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:4323: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:4328: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:4333: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:4338: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:4343: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:4348: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:4353: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:4358: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:4363: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:4368: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:4373: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:4378: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:4383: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:4388: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:4393: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:4398: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:4403: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:4408: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:4413: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:4418: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:4423: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:4428: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:4433: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:4438: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:4443: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:4448: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:4453: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:4458: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:4463: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:4468: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:4473: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:4478: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:4483: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:4488: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:4493: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:4498: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:4503: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:4508: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:4513: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:4518: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:4523: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:4528: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:4533: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:4538: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:4543: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:4548: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:4553: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:4558: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:4563: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:4568: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:4573: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:4578: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:4583: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:4588: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:4593: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:4598: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:4603: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:4608: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:4613: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:4618: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:4623: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:4628: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:4633: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:4638: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:4643: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:4648: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:4653: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:4658: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:4663: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:4668: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:4673: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:4678: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:4683: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:4688: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:4693: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:4698: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:4703: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:4708: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:4713: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:4718: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:4723: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:4728: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:4733: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:4738: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:4743: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:4748: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:4753: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:4758: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:4763: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:4768: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:4773: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:4778: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:4783: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:4788: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:4793: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:4798: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:4803: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:4808: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:4813: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:4818: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:4823: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:4828: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:4833: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:4838: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:4843: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:4848: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:4853: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:4858: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:4863: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:4868: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:4873: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:4878: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:4883: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:4888: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:4893: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:4898: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:4903: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:4908: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:4913: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:4918: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:4923: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:4928: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:4933: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:4938: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:4943: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:4948: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:4953: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:4958: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:4963: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:4968: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:4973: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:4978: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:4983: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:4988: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:4993: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:4998: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:5003: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:5008: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:5013: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:5018: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:5023: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:5028: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:5033: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:5038: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:5043: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:5048: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:5053: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:5058: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:5063: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:5068: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:5073: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:5078: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:5083: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:5088: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:5093: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:5098: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:5103: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:5108: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:5113: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:5118: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:5123: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:5128: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:5133: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:5138: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:5143: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:5148: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:5153: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:5158: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:5163: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:5168: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:5173: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:5178: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:5183: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:5188: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:5193: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:5198: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:5203: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:5208: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:5213: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:5218: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:5223: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:5228: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:5233: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:5238: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:5243: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:5248: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:5253: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:5258: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:5263: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:5268: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:5273: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:5278: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:5283: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:5288: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:5293: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:5298: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:5303: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:5308: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:5313: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:5318: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:5323: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:5328: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:5333: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:5338: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:5343: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:5348: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:5353: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:5358: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:5363: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:5368: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:5373: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:5378: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:5383: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:5388: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:5393: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:5398: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:5403: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:5408: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:5413: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:5418: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:5423: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:5428: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:5433: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:5438: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:5443: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:5448: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:5453: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:5458: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:5463: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:5468: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:5473: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:5478: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:5483: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:5488: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:5493: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:5498: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:5503: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:5508: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:5513: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:5518: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:5523: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:5528: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:5533: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:5538: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:5543: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:5548: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:5553: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:5558: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:5563: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:5568: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:5573: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:5578: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:5583: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:5588: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:5593: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:5598: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:5603: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:5608: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:5613: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:5618: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:5623: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:5628: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:5633: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:5638: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:5643: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:5648: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:5653: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:5658: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:5663: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:5668: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:5673: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:5678: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:5683: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:5688: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:5693: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:5698: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:5703: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:5708: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:5713: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:5718: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:5723: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:5728: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:5733: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:5738: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:5743: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:5748: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:5753: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:5758: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:5763: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:5768: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:5773: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:5778: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:5783: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:5788: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:5793: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:5798: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:5803: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:5808: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:5813: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:5818: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:5823: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:5828: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:5833: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:5838: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:5843: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:5848: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:5853: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:5858: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:5863: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:5868: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:5873: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:5878: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:5883: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:5888: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:5893: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:5898: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:5903: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:5908: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:5913: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:5918: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:5923: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:5928: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:5933: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:5938: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:5943: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:5948: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:5953: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:5958: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:5963: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:5968: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:5973: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:5978: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:5983: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:5988: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:5993: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:5998: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:6003: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:6008: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:6013: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:6018: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:6023: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:6028: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:6033: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:6038: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:6043: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:6048: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:6053: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:6058: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:6063: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:6068: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:6073: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:6078: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:6083: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:6088: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:6093: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:6098: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:6103: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:6108: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:6113: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:6118: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:6123: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:6128: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:6133: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:6138: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:6143: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:6148: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:6153: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:6158: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:6163: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:6168: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:6173: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:6178: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:6183: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:6188: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:6193: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:6198: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:6203: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:6208: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:6213: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:6218: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:6223: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:6228: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:6233: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:6238: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:6243: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:6248: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:6253: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:6258: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:6263: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:6268: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:6273: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:6278: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:6283: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:6288: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:6293: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:6298: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:6303: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:6308: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:6313: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:6318: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:6323: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:6328: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:6333: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:6338: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:6343: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:6348: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:6353: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:6358: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:6363: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:6368: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:6373: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:6378: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:6383: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:6388: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:6393: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:6398: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:6403: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:6408: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:6413: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:6418: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:6423: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:6428: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:6433: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:6438: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:6443: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:6448: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:6453: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:6458: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:6463: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:6468: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:6473: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:6478: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:6483: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:6488: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:6493: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:6498: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:6503: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:6508: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:6513: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:6518: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:6523: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:6528: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:6533: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:6538: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:6543: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:6548: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:6553: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:6558: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:6563: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:6568: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:6573: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:6578: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:6583: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:6588: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:6593: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:6598: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:6603: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:6608: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:6613: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:6618: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:6623: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:6628: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:6633: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:6638: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:6643: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:6648: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:6653: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:6658: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:6663: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:6668: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:6673: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:6678: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:6683: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:6688: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:6693: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:6698: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:6703: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:6708: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:6713: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:6718: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:6723: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:6728: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:6733: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:6738: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:6743: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:6748: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:6753: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:6758: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:6763: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:6768: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:6773: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:6778: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:6783: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:6788: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:6793: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:6798: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:6803: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:6808: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:6813: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:6818: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:6823: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:6828: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:6833: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:6838: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:6843: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:6848: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:6853: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:6858: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:6863: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:6868: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:6873: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:6878: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:6883: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:6888: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:6893: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:6898: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:6903: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:6908: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:6913: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:6918: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:6923: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:6928: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:6933: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:6938: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:6943: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:6948: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:6953: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:6958: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:6963: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:6968: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:6973: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:6978: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:6983: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:6988: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:6993: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:6998: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:7003: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:7008: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:7013: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:7018: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:7023: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:7028: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:7033: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:7038: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:7043: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:7048: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:7053: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:7058: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:7063: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:7068: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:7073: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:7078: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:7083: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:7088: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:7093: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:7098: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:7103: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:7108: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:7113: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:7118: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:7123: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:7128: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:7133: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:7138: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:7143: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:7148: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:7153: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:7158: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:7163: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:7168: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:7173: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:7178: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:7183: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:7188: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:7193: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:7198: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:7203: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:7208: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:7213: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:7218: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:7223: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:7228: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:7233: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:7238: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:7243: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:7248: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:7253: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:7258: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:7263: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:7268: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:7273: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:7278: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:7283: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:7288: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:7293: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:7298: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:7303: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:7308: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:7313: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:7318: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:7323: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:7328: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:7333: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:7338: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:7343: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:7348: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:7353: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:7358: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:7363: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:7368: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:7373: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:7378: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:7383: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:7388: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:7393: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:7398: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:7403: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:7408: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:7413: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:7418: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:7423: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:7428: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:7433: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:7438: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:7443: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:7448: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:7453: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:7458: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:7463: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:7468: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:7473: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:7478: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:7483: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:7488: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:7493: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:7498: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:7503: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:7508: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:7513: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:7518: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:7523: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:7528: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:7533: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:7538: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:7543: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:7548: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:7553: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:7558: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:7563: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:7568: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:7573: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:7578: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:7583: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:7588: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:7593: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:7598: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:7603: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:7608: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:7613: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:7618: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:7623: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:7628: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:7633: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:7638: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:7643: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:7648: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:7653: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:7658: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:7663: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:7668: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:7673: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:7678: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:7683: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:7688: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:7693: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:7698: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:7703: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:7708: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:7713: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:7718: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:7723: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:7728: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:7733: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:7738: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:7743: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:7748: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:7753: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:7758: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:7763: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:7768: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:7773: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:7778: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:7783: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:7788: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:7793: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:7798: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:7803: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:7808: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:7813: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:7818: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:7823: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:7828: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:7833: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:7838: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:7843: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:7848: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:7853: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:7858: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:7863: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:7868: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:7873: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:7878: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:7883: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:7888: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:7893: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:7898: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:7903: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:7908: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:7913: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:7918: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:7923: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:7928: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:7933: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:7938: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:7943: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:7948: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:7953: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:7958: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:7963: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:7968: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:7973: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:7978: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:7983: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:7988: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:7993: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:7998: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:8003: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:8008: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:8013: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:8018: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:8023: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:8028: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:8033: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:8038: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:8043: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:8048: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:8053: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:8058: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:8063: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:8068: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:8073: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:8078: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:8083: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:8088: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:8093: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:8098: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:8103: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:8108: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:8113: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:8118: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:8123: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:8128: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:8133: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:8138: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:8143: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:8148: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:8153: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:8158: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:8163: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:8168: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:8173: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:8178: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:8183: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:8188: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:8193: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:8198: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:8203: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:8208: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:8213: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:8218: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:8223: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:8228: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:8233: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:8238: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:8243: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:8248: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:8253: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:8258: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:8263: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:8268: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:8273: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:8278: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:8283: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:8288: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:8293: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:8298: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:8303: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:8308: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:8313: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:8318: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:8323: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:8328: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:8333: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:8338: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:8343: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:8348: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:8353: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:8358: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:8363: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:8368: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:8373: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:8378: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:8383: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:8388: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:8393: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:8398: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:8403: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:8408: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:8413: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:8418: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:8423: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:8428: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:8433: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:8438: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:8443: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:8448: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:8453: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:8458: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:8463: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:8468: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:8473: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:8478: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:8483: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:8488: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:8493: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:8498: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:8503: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:8508: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:8513: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:8518: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:8523: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:8528: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:8533: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:8538: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:8543: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:8548: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:8553: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:8558: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:8563: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:8568: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:8573: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:8578: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:8583: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:8588: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:8593: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:8598: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:8603: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:8608: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:8613: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:8618: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:8623: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:8628: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:8633: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:8638: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:8643: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:8648: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:8653: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:8658: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:8663: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:8668: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:8673: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:8678: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:8683: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:8688: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:8693: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:8698: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:8703: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:8708: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:8713: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:8718: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:8723: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:8728: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:8733: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:8738: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:8743: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:8748: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:8753: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:8758: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:8763: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:8768: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:8773: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:8778: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:8783: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:8788: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:8793: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:8798: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:8803: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:8808: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:8813: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:8818: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:8823: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:8828: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:8833: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:8838: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:8843: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:8848: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:8853: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:8858: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:8863: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:8868: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:8873: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:8878: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:8883: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:8888: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:8893: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:8898: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:8903: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:8908: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:8913: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:8918: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:8923: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:8928: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:8933: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:8938: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:8943: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:8948: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:8953: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:8958: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:8963: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:8968: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:8973: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:8978: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:8983: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:8988: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:8993: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:8998: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:9003: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:9008: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:9013: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:9018: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:9023: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:9028: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:9033: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:9038: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:9043: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:9048: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:9053: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:9058: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:9063: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:9068: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:9073: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:9078: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:9083: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:9088: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:9093: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:9098: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:9103: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:9108: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:9113: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:9118: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:9123: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:9128: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:9133: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:9138: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:9143: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:9148: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:9153: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:9158: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:9163: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:9168: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:9173: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:9178: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:9183: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:9188: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:9193: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:9198: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:9203: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:9208: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:9213: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:9218: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:9223: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:9228: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:9233: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:9238: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:9243: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:9248: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:9253: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:9258: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:9263: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:9268: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:9273: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 "/Users/sbasu1/packages/macports/var/macports/build/_Users_sbasu1_packages_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-scipy/py311-scipy/work/scipy-1.10.1" && /Users/sbasu1/packages/macports/Library/Frameworks/Python.framework/Versions/3.11/bin/python3.11 setup.py --no-user-cfg build -j4 
:info:build Exit code: 1
:error:build Failed to build py311-scipy: command execution failed
:debug:build Error code: CHILDSTATUS 33349 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 8)
:debug:build     invoked from within
:debug:build "$procedure $targetname"
:error:build See /Users/sbasu1/packages/macports/var/macports/logs/_Users_sbasu1_packages_macports_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_python_py-scipy/py311-scipy/main.log for details.