Add explicit casts to silence compiler warnings

for #1710

for #1710

Introduce blasabs macro and use it to switch between abs and labs for INTERFACE64

Fixes two calls that were using `fabs` on a `long double` argument rather than `fabsl`, which looks like it is doing an unintentional truncation to `double` precision.

I don't have as many benchmarks for these as for gemm, but it should still
make a difference for small matrices.

Always checking num_cpu_avail() regardless of whether threading will actually
be used adds noticeable overhead for small matrices.  Most other uses of
num_cpu_avail() do so only if threading will be used, so do the same here.

copies daxpy improvement from #27, see #1560

Disable multithreading in ztrmv

BLAS-Tester shows that the same problem exists as with DTRMV (issue #1332)

* Rewrite ROTMG based on the new implementation in GONUM based on the algorithm proposed by Tim Hopkins, see issue 1452 for the reference
* Correct ROTMG utest for issue1452 and add another from gonum, also correct transposition of expected and observed values in error messages

Fixes #1452 and is more in line with how ATLAS does it. The earlier fix from #356 only moved the bug elsewhere, but we will never want the iterative rescaling to change the dflag setting and variable associations with each cycle.

as a (hopefully temporary) workaround for #1332

Eliminate mode variable where not needed in syrk interface

Modify complex CBLAS functions to take void pointers instead of float or double arguments (to bring the prototypes in line with netlib and other implementations' cblas.h)

Fix cols/rows mixup in omatcopy 2nd step for BlasTrans cases

Equivalent of #1244 (issue #899) for the non-complex cases. Fixes #1289

Optimized standard Blas Level-1,2 (excluding nrm2 functions) for z13 (double precision). Issue 884

Use in-place transform shortcut only if matrix is square

This is MicMuc's patch from #899

* fix unlikely memleak in zimatcopy interface

* fix only unlikely memleak in zimatcopy interface

* fix only unlikely memleak in zimatcopy interface

* Hopefully, because this was found by error and trial (dark magic)
* Ref #786

added experimental support for optimized lapack fortran functions

If OpenBLAS is built using add_subdirectory(OpenBlas) as part of another project
then the paths set by CMAKE_XXX_DIR are relative to the parent project
and not the OpenBLAS project.