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.

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

[oneMKL][BLAS] value_or_pointer wrapper for BLAS USM scalar parameters #503

Merged
merged 2 commits into from
Sep 29, 2023

Conversation

andrewtbarker
Copy link
Contributor

Allow either values or pointers for scalar parameters to BLAS functions with USM interfaces.

This would allow users to provide values in device memory for these scalar parameters.

``value_or_pointer<T>`` wrapper to enable either pointers or values
to be passed to routines that take a scalar parameter. This type is in
the ``oneapi::mkl::`` namespace and defined in the header file
``oneapi/mkl/types.hpp``.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems to be too specific to oneMKL product. For spec, should we consider removing this or make it more general?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed, I've removed that sentence.

Copy link
Contributor

@mmeterel mmeterel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR. Overall, looks good. I added one question.

@mmeterel mmeterel merged commit 950b890 into uxlfoundation:main Sep 29, 2023
3 checks passed
aepanchi pushed a commit to aepanchi/oneAPI-spec that referenced this pull request Oct 31, 2023
uxlfoundation#503)

* [oneMKL][BLAS] value_or_pointer wrapper for BLAS UUSM scalar parameters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants