Add new blas/lapack interfaces#6658
Merged
mohanchen merged 21 commits intodeepmodeling:developfrom Nov 6, 2025
Merged
Conversation
Collaborator
|
@Cstandardlib Will this modification affect toolchain installation ? |
Collaborator
Author
|
@QuantumMisaka This modification only add some routines/tests, and do not introduce new dependencies, so I guess there will be no impacts on toolchain. |
mohanchen
approved these changes
Nov 6, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What's changed?
lapackConnectorandcuSolverConnector.Lists of interfaces
BLAS
blas_copyblas_nrm2Standard interface of BLAS
copyandnrm2.LAPACK
lapack_getrf_inplaceIn-place QR factorization combining
geqrfandorgqr.Unit Tests and/or Case Tests for my changes
container::kernelsBLAS/LAPACK interface.Any changes of core modules? (ignore if not applicable)
Note
cuSolverprovides two different APIs; legacy and generic. The generic APIs might reduce the complexity ofcuSolverConnectorimplementation. This depends on some type traits defined in the cuSolver header cusolver_utils.h.cuSolverConnectorinterface, but for now not supported.