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
BLIS has the ability to toggle ILP64, etc. but there are no hooks for it.
Another option relates to complex return value ABI, since BLIS does not yet correctly autodetect that for all Fortran compilers (flame/blis#765). However, this issue is less critical until PGI/NVHPC Fortran is no longer a conflict (or perhaps this is the reason it is a conflict).
Rationale
NWChem, among other codes, likes ILP64 BLAS.
Description
The options are there. They just need the package file to activate them.
-b SIZE, --blas-int-size=SIZE
Set the size (in bits) of integer types in external
BLAS and CBLAS interfaces, if enabled. The default
integer type size used in BLAS/CBLAS is 32 bits.
--complex-return=gnu|intel
Specify the way in which complex numbers are returned
from Fortran functions, either "gnu" (return in
registers) or "intel" (return via hidden argument).
If not specified and the environment variable FC is set,
attempt to determine the return type from the compiler.
Otherwise, the default is "gnu".
Additional information
I will try to work on this soon.
General information
I have searched the issues of this repo and believe this is not a duplicate
The text was updated successfully, but these errors were encountered:
Summary
BLIS has the ability to toggle ILP64, etc. but there are no hooks for it.
Another option relates to complex return value ABI, since BLIS does not yet correctly autodetect that for all Fortran compilers (flame/blis#765). However, this issue is less critical until PGI/NVHPC Fortran is no longer a conflict (or perhaps this is the reason it is a conflict).
Rationale
NWChem, among other codes, likes ILP64 BLAS.
Description
The options are there. They just need the package file to activate them.
Additional information
I will try to work on this soon.
General information
The text was updated successfully, but these errors were encountered: