Skip to content

Commit

Permalink
Merge pull request #306 from amd-jnovotny/link-checker-develop
Browse files Browse the repository at this point in the history
Fix dead link to rocSOLVER API
  • Loading branch information
amd-jnovotny authored Jul 26, 2024
2 parents ffef53c + 0504f42 commit 3de3b56
Show file tree
Hide file tree
Showing 4 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion docs/reference/api/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ hipSOLVER regular API

This document provides the method signatures for wrapper functions that are currently implemented in hipSOLVER.
For a complete description of the functions' behavior and arguments, see the corresponding backend documentation
at `cuSOLVER API <https://docs.nvidia.com/cuda/cusolver/>`_ and/or :doc:`rocSOLVER API <rocsolver:reference/index>`.
at `cuSOLVER API <https://docs.nvidia.com/cuda/cusolver/>`_ and/or :doc:`rocSOLVER API <rocsolver:reference/intro>`.

The hipSOLVER API is designed to be similar to the cuSOLVER and rocSOLVER interfaces, but it requires some minor adjustments to ensure
the best performance out of both backends. Generally, this involves the addition of workspace parameters and some additional API methods.
Expand Down
2 changes: 1 addition & 1 deletion docs/reference/dense-api/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ hipSOLVER compatibility API - Dense Matrices

This document provides the method signatures for the wrapper functions that are currently implemented in hipSOLVER.
For a complete description of the functions' behavior and arguments, see the corresponding backend documentation
at `cuSOLVER API <https://docs.nvidia.com/cuda/cusolver/>`_ and/or `rocSOLVER API <https://rocm.docs.amd.com/projects/rocSOLVER/en/latest/api/index.html>`_.
at `cuSOLVER API <https://docs.nvidia.com/cuda/cusolver/>`_ and/or :doc:`rocSOLVER API <rocsolver:reference/intro>`.

For ease of porting from existing cuSOLVER applications to hipSOLVER, functions in the hipsolverDn compatibility API are designed to have
method signatures that are consistent with the cusolverDn interface. However, :ref:`performance issues <dense_performance>` may arise when
Expand Down
2 changes: 1 addition & 1 deletion docs/reference/refactor-api/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ hipSOLVER Compatibility API - Refactorization

This document provides the method signatures for the wrapper functions that are currently implemented in hipSOLVER.
For a complete description of the functions' behavior and arguments, see the corresponding backend documentation
at `cuSOLVER API <https://docs.nvidia.com/cuda/cusolver/index.html#cuds-api>`_ and/or `rocSOLVER API <https://rocm.docs.amd.com/projects/rocSOLVER/en/latest/index.html>`_.
at `cuSOLVER API <https://docs.nvidia.com/cuda/cusolver/index.html#cuds-api>`_ and/or :doc:`rocSOLVER API <rocsolver:reference/intro>`.

For ease of porting from existing cuSOLVER applications to hipSOLVER, functions in the hipsolverRf compatibility API are designed to have
method signatures that are consistent with the cusolverRf interface. At present, equivalent functions have not been added to hipSOLVER's regular API.
Expand Down
2 changes: 1 addition & 1 deletion docs/reference/sparse-api/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ hipSOLVER compatibility API - Sparse Matrices

This document provides the method signatures for the wrapper functions that are currently implemented in hipSOLVER.
For a complete description of the functions' behavior and arguments, see the corresponding backend documentation
at `cuSOLVER API <https://docs.nvidia.com/cuda/cusolver/index.html#cuds-api>`_ and/or `rocSOLVER API <https://rocm.docs.amd.com/projects/rocSOLVER/en/latest/api/index.html>`_.
at `cuSOLVER API <https://docs.nvidia.com/cuda/cusolver/index.html#cuds-api>`_ and/or :doc:`rocSOLVER API <rocsolver:reference/intro>`.

For ease of porting from existing cuSOLVER applications to hipSOLVER, functions in the hipsolverSp compatibility API are designed to have
method signatures that are consistent with the cusolverSp interface. At present, equivalent functions have not been added to hipSOLVER's
Expand Down

0 comments on commit 3de3b56

Please sign in to comment.