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
When calling kernels from DPLASMA on GPU, either setup_parsec/cleanup_parsec or parsec_info_register/parsec_info_unregister need to be called in users' codes. Otherwise, DPLASMA::CUDA::HANDLES will not be registered.
It would be better to hide this on the users' side, so they can directly call APIs from DPLASMA.
To Reproduce
Steps to reproduce the behavior:
Checkout version 'commit-hash'
Compile with the following options '....' [e.g., head config.log]
Run test '....' [e.g. ctest --output-on-failure -R xyz]
See error
Expected behavior
A clear and concise description of what you expected to happen.
Environment (please complete the following information):
DPLASMA version: [e.g. git hash]
PaRSEC status: external/internal and version: [e.g., git hash]
OS: [e.g. CentOS/7]
Compiler: [e.g. GCC/7.3.0]
MPI version: [e.g. Open MPI/4.1.2]
Additional context
Add any other context about the problem here.
The content of the config.log file can be useful in some cases.
The text was updated successfully, but these errors were encountered:
Describe the bug
When calling kernels from DPLASMA on GPU, either
setup_parsec
/cleanup_parsec
orparsec_info_register
/parsec_info_unregister
need to be called in users' codes. Otherwise,DPLASMA::CUDA::HANDLES
will not be registered.It would be better to hide this on the users' side, so they can directly call APIs from DPLASMA.
To Reproduce
Steps to reproduce the behavior:
head config.log
]ctest --output-on-failure -R xyz
]Expected behavior
A clear and concise description of what you expected to happen.
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The content of the
config.log
file can be useful in some cases.The text was updated successfully, but these errors were encountered: