In addition to testing fork safety on non-OpenMP builds, test it when
omp_pause_resource_all() is available to release the locks.

OpenMP 5.0 introduced the function omp_pause_resource_all that instructs
the runtime to "relinquish resources used by OpenMP on all devices". In
practice, these resources include the locks that would otherwise trip up
the runtime after a fork(). Releasing these resources in a function
called by pthread_atfork() makes it possible for the child process to
continue functioning after the runtime automatically re-acquires its
resources.

Thread safety: blas_thread_shutdown doesn't check whether there are
other BLAS operations running in parallel, so this isn't any less safe
than before with respect to OpenBLAS function calls. On the other hand,
if there are other OpenMP operations in progress, asking the runtime to
pause may result in unspecified behaviour. A hard pause is allowed to
deallocate threadprivate variables too.

Assume that the ctest3.c program successfully compiling and linking
means that the function is available.

Support for SGEMM_DIRECT Kernel based on SME1

Ensure that gmake builds with flang-new link the flang runtime into the shared library

Fix the CMake build to define USE_TRMM for RISCV64 targets as well

Revert "Fix potential inaccuracy in multithreaded level3 related to SWITCH_RATIO"

CI: remove the express NeoverseN2 target from the Cobalt100 job in the gh workflow

* Added ARMV9SME target
* Added SGEMM_DIRECT kernel based on SME1

Refined GESV Parallelization Logic for Windows on ARM64

Add -O2 to flang flags when building on WoA in Release mode

LoongArch64: Fixed lapack test for LA264

Fix SGEMV on POWER8 by reverting to the non-vectorized earlier code

CirrusCI: Update FreeBSD jobs to 14.2

When the data type is single-precision real or single-precision complex,
converting it to double precision does not prevent overflow (as exposed in LAPACK tests).
The only solution is to follow C's approach: find the maximum value in the
array and divide each element by that maximum to avoid this issue

Fixed the error when the stride is zero

Do not check whether the input parameters c and s are zero,
as this may cause errors with special values (same as scal).
Although OpenBLAS's own test suite doesn't catch this, it will
cause LAPACK test cases to fail.

Fixed incorrect store operation

Signed-off-by: gxw <guxiwei-hf@loongson.cn>

Fixed index retrieval issue when there are
identical maximum absolute values

Signed-off-by: Hao Chen <chenhao@loongson.cn>
Signed-off-by: gxw <guxiwei-hf@loongson.cn>

Fixed incorrect register usage in instructions

Signed-off-by: gxw <guxiwei-hf@loongson.cn>

Fixed register zeroing operation

Signed-off-by: Hao Chen <chenhao@loongson.cn>
Signed-off-by: gxw <guxiwei-hf@loongson.cn>

Handle INCX=0 in ?NRM2

Disable extended utests for CSROT/ZDROT that invoke undefined behavior

Add SBGEMM for arm neoversev1

Ensure that GEMMTR name appears in XERBLA if GEMMT was called as such

Signed-off-by: Ye Tao <ye.tao@arm.com>

fix signedness of pointer to integer type passed to blas_lock()

* AzureCI: Add LLVM/flang-new build on OSX-x86_64
* distinguish classic flang from flang-new in name based recognition

Fix CMake build for PPCG4 breaking due to unparsable KERNEL file