You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My machine has Xeon E7 4870 processors, which use the Nehalem-based Westmere microarchitecture. However, OpenBLAS built with DYNAMIC_ARCH appears to identify them as Atom cores. The output of openblas_get_config() is:
OpenBLAS 0.3.5 USE64BITINT DYNAMIC_ARCH NO_AFFINITY Atom MAX_THREADS=32
export OPENBLAS_CORETYPE=Nehalem makes no difference
Option #2 looks cleaner to me (though neither will solve the "problem" with a custom DYNAMIC_LIST - which would require a nasty cascade of ifdefs that is probably not worthwile to implement)
My machine has Xeon E7 4870 processors, which use the Nehalem-based Westmere microarchitecture. However, OpenBLAS built with
DYNAMIC_ARCH
appears to identify them as Atom cores. The output ofopenblas_get_config()
is:export OPENBLAS_CORETYPE=Nehalem
makes no differenceI think the actual problem is that with
DYNAMIC_ARCH
but notDYNAMIC_OLDER
,gotoblas_ATOM
is aliased togotoblas_NEHALEM
, andgotoblas_coretype()
checks forgotoblas == &gotoblas_ATOM
beforegotoblas == &gotoblas_NEHALEM
:https://github.com/xianyi/OpenBLAS/blob/9d5079008f964d0be08708dc3785ebcf5b7bf68b/driver/others/dynamic.c#L767-L771
Seems like the solution would be one of the following:
gotoblas_<ARCH>
identifiers that could be aliases are checked last ingotoblas_corename()
, orgotoblas_corename()
depending on compiler flagsThe text was updated successfully, but these errors were encountered: