Introduction#
Library overview#
hipSOLVER is an open-source marshalling library for LAPACK routines on the GPU. It sits between a backend library and the user application, marshalling inputs to and outputs from the backend library so that the user application remains unchanged when using different backends. Currently, two backend libraries are supported by hipSOLVER: NVIDIA’s cuSOLVER library and AMD’s open-source rocSOLVER library.
The regular hipSOLVER API is a thin wrapper layer around the different backends. As such, it is not expected to introduce significant overhead. However, its main purpose is portability, so when performance is critical, directly using the library backend corresponding to the given architecture is recommended.
Another purpose of hipSOLVER is to facilitate the translation of cuSOLVER applications to AMD’s open source ROCm platform ecosystem. To that end, hipSOLVER also includes hipsolverDn and hipsolverRf compatibility APIs with method signatures that match exactly those of cuSOLVER. For more details see the section Using hipSOLVER.
Currently implemented functionality#
The hipSOLVER library remains in active development. New features are being continuously added, with new functionality documented at each release of the ROCm platform.
The following tables summarize the wrapper functions that are implemented in the regular API for the different supported precisions in hipSOLVER’s latest release. Most of these functions have a corresponding version in the compatibility API, where applicable.
LAPACK auxiliary functions#
Function |
single |
double |
single complex |
double complex |
---|---|---|---|---|
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
Function |
single |
double |
single complex |
double complex |
---|---|---|---|---|
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
LAPACK main functions#
Function |
single |
double |
single complex |
double complex |
---|---|---|---|---|
x |
x |
x |
x |
|
x |
x |
x |
x |
|
x |
x |
x |
x |
|
x |
x |
x |
x |
|
x |
x |
x |
x |
|
x |
x |
x |
x |
|
x |
x |
x |
x |
|
x |
x |
x |
x |
Function |
single |
double |
single complex |
double complex |
---|---|---|---|---|
x |
x |
x |
x |
|
x |
x |
x |
x |
Function |
single |
double |
single complex |
double complex |
---|---|---|---|---|
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
x |
x |
|
x |
x |
x |
x |
Function |
single |
double |
single complex |
double complex |
---|---|---|---|---|
x |
x |
x |
x |
|
x |
x |
x |
x |
|
x |
x |
x |
x |
|
x |
x |
x |
x |
|
x |
x |
x |
x |
|
x |
x |
x |
x |
|
x |
x |
x |
x |
|
x |
x |
x |
x |
|
x |
x |
x |
x |
|
x |
x |
x |
x |
Function |
single |
double |
single complex |
double complex |
---|---|---|---|---|
x |
x |
x |
x |
|
x |
x |
x |
x |
Function |
single |
double |
single complex |
double complex |
---|---|---|---|---|
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
Function |
single |
double |
single complex |
double complex |
---|---|---|---|---|
x |
x |
x |
x |
|
x |
x |
x |
x |
LAPACK-like functions#
Function |
single |
double |
single complex |
double complex |
---|---|---|---|---|
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
Function |
single |
double |
single complex |
double complex |
---|---|---|---|---|
x |
x |
x |
x |
|
x |
x |
x |
x |
|
x |
x |
x |
x |
|
x |
x |
x |
x |
Compatibility-only functions#
The following tables summarize the wrapper functions that are provided only in the compatibility APIs. These wrappers are supported in rocSOLVER but either by equivalent functions that use different algorithmic approaches, or by functionality that is not fully exposed in the public API. For these reasons, at present, the corresponding wrappers are not provided in the regular hipSOLVER API.
Partial eigensolver functions#
Partial eigensolvers have been implemented in rocSOLVER, but at present they do not use a divide-and-conquer approach.
Function |
single |
double |
single complex |
double complex |
---|---|---|---|---|
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
|||
x |
x |
Partial SVD functions#
Partial SVD has been implemented in rocSOLVER, but at present it does not use an approximate algorithm, nor does it compute the residual norm.
Function |
single |
double |
single complex |
double complex |
---|---|---|---|---|
x |
x |
x |
x |
|
x |
x |
x |
x |
Refactorization routines#
Refactorization routines and direct solvers for sparse matrices are in the very earliest stages of development. At present, some of the functionality is not exposed as part of rocSOLVER’s public API and is subject to change. Refer to the hipsolverRf compatibility API for a full listing of supported functions.