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

Simplify build instructions for Windows on Arm

Fix compilation with BUILD_BFLOAT16 enabled

Simplify gemv_t_sve_v1x3 kernel

Add thread throttling profile for SGEMV on `NEOVERSEV1`

Fix Windows on ARM build instructions

The command as merged uses the compiler target as the compiler path.

I have run and tested a build with this command.

@Mugundanmcw - is this correct?

Small gemm kernel improvements for AArch64

Add thread throttling profile for SGEMM on NEOVERSEV1

Fix "make install" operation when CPP_THREAD_SAFETY_TEST is selected

LoongArch64: Fixed cmake

Further rearranged the rotm kernel for the different architectures.

Fix CMake interpretation of KERNEL file variables relevant to WoA

Signed-off-by: tingbo.liao <tingbo.liao@starfivetech.com>

Get ARM64 TARGET information from the registry on Windows

MIPS64 CI :fix breakage from inadvertent line join in yml file

* Protect align directives in assembly files that are currently problematic with LLVM on WoA

* use the armv8 zdot on WoA to work around other LLVM issues

* Add NeoverseN2 build

Optimize the gemm_tcopy_8_rvv to be compatible with the vlens 128 and 256.

Signed-off-by: tingbo.liao <tingbo.liao@starfivetech.com>

LoongArch64: Update symv lsx version

LoongArch64: Fix dsymv and ssymv LASX version

Azure CI: update deprecated macos-12 jobs to macos-13 image

"fmov.d $f2, $f4" leaves all the bits higher than the 63-th bit
unpredictable but it's obvious that the following code uses the value of
those high bits.  We actually want to replicate the lower 64 bits here,
so we should use xvreplve0.d instead.

LA464 (Loongson 3[A-Z]-5000) happens to replicate them for us due to
some uarch internal details so the issue was not detected, but for LA664
(Loongson 3[A-Z]-6000) and future uarch we need to do things correctly
or we end up getting a lot of test failures.

Closes: https://bbs.aosc.io/t/topic/302
Signed-off-by: Xi Ruoyao <xry111@xry111.site>