Remove an unused variable from several LAPACKE 2stage_work functions

Copied from Reference-LAPACK PR283

Copied from Reference-LAPACK PR283

Copied from Reference-LAPACK PR283

fix small typo in strmm_ LN

Follow netlib renaming/aliasing CBLAS_ORDER to CBLAS_LAYOUT

Fix ARMV8 cross-compilation for IOS

to avoid having to change all instances of enum CBLAS_ORDER in this file

fixes #1754

Assume cross-compilation if host and target os differ

fixes 1674

Set USE_TRMM for all ZARCH variants to fix TRMM faults with zarch-gen…

Fix missing replacements of ILAENV by ILAENV_2STAGE (lapack PR 272)

fixes #1743

This could cause spurious "parameter has an illegal value" errors in DSYEVR and related routines, see https://github.com/Reference-LAPACK/lapack/issues/262

Add combination of old and new thread memory code selectable by new option USE_TLS

detect z14 arch on s390x

add short blurb about avx512 and needed compiler to README

Add an AVX512 enabled DSYMV (L) function

Add an AVX512 enabled DGEMV (n)  function

Fix typo in sdot function

Add an AVX512 enabled DSCAL function

Disable zgemv scale in gemv benchmark by default

written in C intrinsics for best readability.
(the same C code works for Haswell as well)

For logistical reasons the code falls back to the existing
haswell AVX2 implementation if the GCC or LLVM compiler is not new enough

written in C intrinsics for best readability.
(the same C code works for Haswell as well)

For logistical reasons the code falls back to the existing
haswell AVX2 implementation if the GCC or LLVM compiler is not new enough

it looks like my previous pull request was short the final commit;
fix a typo in sdot

written in C intrinsics for best readability.
(the same C code works for Haswell as well)

For logistical reasons the code falls back to the existing
haswell AVX2 implementation if the GCC or LLVM compiler is not new enough

Add a AVX512 enabled SAXPY/DAXPY functions

Add an AVX512 enabled SDOT function

Add changes from the 0.3.x releases

fixes #1727

written in C intrinsics for best readability.
(the same C code works for Haswell as well)

For logistical reasons the code falls back to the existing
haswell AVX2 implementation if the GCC or LLVM compiler is not new enough

written in C intrinsics for best readability.
(the same C code works for Haswell as well)

For logistical reasons the code falls back to the existing
haswell AVX2 implementation if the GCC or LLVM compiler is not new enough