The user can use char * openblas_get_config() or char * openblas_get_corename().

Conflicts:
	driver/others/memory.c

This is MinGW convention.

Signed-off-by: Timothy Gu <timothygu99@gmail.com>

Signed-off-by: Timothy Gu <timothygu99@gmail.com>

Adding $(EXTRALIB) adds this flag when things are built with
msys2 on windows. Without this the build fails.

Merge branch 'TimothyGu-develop' into develop

Signed-off-by: Timothy Gu <timothygu99@gmail.com>

They are not used anymore since 3eb5af1.

Signed-off-by: Timothy Gu <timothygu99@gmail.com>

Signed-off-by: Timothy Gu <timothygu99@gmail.com>

Signed-off-by: Timothy Gu <timothygu99@gmail.com>

Signed-off-by: Timothy Gu <timothygu99@gmail.com>

Avoids problems of libgfortran not being found.

The aim is to restrict the symbols exported from openBLAS, but for dynamic libraries --retain-symbols-file has the opposite effect intended. It removes symbols from the .symtab section of the library, which is used by tools such as debuggers, profilers, objdump etc. but does not remove them from .dynsym, which is the section used by the runtime when loading the binary.

In short, using --retain-symbols-file like this doesn't prevent symbol leakage but does prevent tools from analyzing applications linked with openBLAS.

This patch improves tool support for openBLAS applications but does not address symbol leakage through .dynsym.

a fortran compiler, please try make ONLY_CBLAS=1.

This mode only compiler CBLAS without BLAS fortran interface and LAPACK.

parallelization model is used by OpenBLAS.

For LAPACKE, use LAPACK_COMPLEX_STRUCTURE.
The reson is lsbcc didn't define complex I in complex.h.

openblas_get_config function returns the configure string.
So far, it supports USE64BITINT, NO_CBLAS, NO_LAPACK, NO_LAPACKE,
DYNAMIC_ARCH, NO_AFFINITY.

Example:
 #include <stdio.h>
extern char * openblas_get_config();
void main()
{
  printf("%s\n",openblas_get_config());
  return;
}

This change adds the missing LAPACKE_[zc]syr routines but does not remove any exported functions.

Added some documentation on how the symbol list is derived and synchronized with
lapack-3.4.1 to minimize the differences.

They are as following,
slabad, dlabad,
slacpy, dlacpy,
slamch, dlamch,
slartg, slartgp, slartgs, dlartg, dlartgp, dlartgs,
slascl, dlascl,
slaset, dlaset.