add raptor lake ids

Fix OPENBLAS_CORETYPE=COOPERLAKE not working in DYNAMIC_ARCH builds

Co-authored-by: Alexis <35051714+amontoison@users.noreply.github.com>

Remove excess initializer (leftover from rework of PR 3793)

x86_64: prevent GCC and Clang from generating FMAs in cscal/zscal.

New sbgemm implementation for Neoverse N2

If e.g. -march=haswell is set in CFLAGS, GCC generates FMAs by default, which
is inconsistent with the microkernels, none of which use FMAs. These
inconsistencies cause a few failures in the LAPACK testcases, where
eigenvalue results with/without eigenvectors are compared.

Moreover using FMAs for multiplication of complex numbers can give surprising
results, see 22aa81f for more information.

This uses the same syntax as used in 22aa81f for zarch (s390x).

1. Use UZP instructions but not gather load and scatter store instructions to get lower latency.
    2. Padding k to a power of 4.

Benchmarks: align malloc'ed buffers.

It stores the pointer, not an offset (that would be an alternative approach).

Benchmarks should allocate with cacheline (often 64 bytes) alignment
to avoid unreliable timings. This technique, storing the offset in the
byte before the pointer, doesn't require C11's aligned_alloc for
compatibility with older compilers.

For example, Glibc's x86_64 malloc returns 16-byte aligned buffers, which is
not sufficient for AVX/AVX2 (32-byte preferred) or AVX512 (64-byte).

Fix pkgconfig file generation for INTERFACE64 builds

Disable the gfortran tree vectorizer for lapack-netlib

Add `OPENBLAS_DEFAULT_NUM_THREADS`

Fix building with only a subset of variable types on Windows

Fix misdetection of gfortran on Cray systems

This allows Julia to set a default number of threads (usually `1`) to be
used when no other thread counts are specified [0], to short-circuit the
default OpenBLAS thread initialization routine that spins up a different
number of threads than Julia would otherwise choose.

The reason to add a new environment variable is that we want to be able
to configure OpenBLAS to avoid performing its initial memory
allocation/thread startup, as that can consume significant amounts of
memory, but we still want to be sensitive to legacy codebases that set
things like `OMP_NUM_THREADS` or `GOTOBLAS_NUM_THREADS`.  Creating a new
environment variable that is openblas-specific and is not already
publicly used to control the overall number of threads of programs like
Julia seems to be the best way forward.

[0] https://github.com/JuliaLang/julia/pull/46844

Support CONSISTENT_FPCSR on aarch64 systems

GitHub Workflows security hardening

Fix MIPS64_GENERIC copyobj declarations for DYNAMIC_ARCH

Signed-off-by: Alex <aleksandrosansan@gmail.com>

Signed-off-by: Alex <aleksandrosansan@gmail.com>

Signed-off-by: Alex <aleksandrosansan@gmail.com>