Field G. Van Zee

@devinamatthews Given that we haven't heard from @tbetcke, I'm okay with merging this commit if you are.

@zerothi Thanks for your feedback. The following scenarios you provided ``` BLIS_NUM_THREADS=X OMP_NUM_THREADS=Y # use X OMP_NUM_THREADS=Y # use Y BLIS_NUM_THREADS=X # use X ``` do indeed reflect how BLIS...

> I guess I should add that none of the devs currently have any plans to deprecate OMP_NUM_THREADS. We could potentially commit to keeping it as an option if uncertainty...

Hi @ivan-pi. To what extent do you need strongly typed function prototypes? My first reaction to this was that this is just the tip of the tip of the tip...

We also just handled a similar request via #812. Your request, @tbetcke, has me wondering about a general-purpose solution that combines the compatibility accommodations for both 812 and your request...

I'm currently implementing the following `configure` option: ``` --omit-symbols=LIST Omit a custom set of compatibility symbols when building BLIS. When given, LIST is parsed as a comma-separated list of symbol...

@tbetcke FYI, I implemented `--omit-symbols=LIST` in #823 (and reimplemented `--enable-scalapck-compat`, and added `--enable-lapack-compat`). Please give it a try when you have the time. Thanks so much.