Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add documentation on ILP64. #453

Merged
merged 2 commits into from
Apr 1, 2024
Merged

Add documentation on ILP64. #453

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b63b0b5
Add documentation on ILP64.
fghoussen Apr 1, 2024
249bd88
Rephrase.
fghoussen Apr 1, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CHANGES
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,8 @@
-- Franck Houssen <[email protected]> Sat, 11 Feb 2023 13:52:57 +0100

[ Franck Houssen ]
* Add documentation on ILP64.

arpack-ng - 3.9.0

[ Vikas Sharma ]
Expand Down
21 changes: 21 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,27 @@ About ILP64 support:
- Sequential arpack supports [ILP64](https://www.intel.com/content/www/us/en/develop/documentation/onemkl-linux-developer-guide/top/linking-your-application-with-onemkl/linking-in-detail/linking-with-interface-libraries/using-the-ilp64-interface-vs-lp64-interface.html), but, parallel arpack doesn't.
- Reminder: you can NOT mix `ILP64` with `LP64`. If you compile `arpack-ng` with `ILP64` (resp. `LP64`) support, you MUST insure your BLAS/LAPACK is compliant with `ILP64` (resp. `LP64`).
- Set `INTERFACE64` at configure time.
- As this can not be automated, you need to make sure that the BLAS/LAPACK libraries you pass to `arpack-ng`:
- Are built with ILP64 support.
In case these ILP64 BLAS/LAPACK libraries have a non-usual name, you must specify them like so:
```
>> ./configure --with-blas=openblas64_ ...
```
- Do export ILP64-flavored symbols. In case these symbols have a non-usual name, you must:
- Check for ILP64 symbols exported by the ILP64 BLAS/LAPACK libraries:
```
>> nm /path/to/libopenblas64_.so | grep scopy64_
0000000000000000 T scopy64_
```
- Specify them to `arpack-ng` using `SYMBOLSUFFIX`:
```
>> SYMBOLSUFFIX=64_ ./configure ...
...
Configuration summary for ARPACK-NG
...
FFLAGS : -fdefault-integer-8 -Dscopy=scopy64_ ...
```
FFLAGS used by `arpack-ng` (built from `SYMBOLSUFFIX` - reported in configure log) *must* redirect the usual symbols to the non-usual ones exported by the ILP64 BLAS/LAPACK libraries: this check is the responsability of the user.

Note for F77/F90 developers:

Expand Down
Loading