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

API to return oneMKL version number? #35

Open
ghost opened this issue Jul 30, 2020 · 2 comments
Open

API to return oneMKL version number? #35

ghost opened this issue Jul 30, 2020 · 2 comments
Labels
accepted The issue/feature is confirmed and going to be implemented feature A request to add a new feature

Comments

@ghost
Copy link

ghost commented Jul 30, 2020

Summary

Should there be an API, callable from both dispatcher (libonemkl.so) and underlying backend libraries to report the oneMKL version supported by each library?

Problem statement

Using oneMKL could involve libraries from multiple vendors (or other sources) to provide backend libraries for different devices. How can a user easily detect if the versions involved are inconsistent with one another? This could occur if one backend has not been updated in line with the dispatcher and other backends, or because of a misconfiguration of LD_LIBRARY_PATH, etc when multiple versions are installed on the system.

Preferred solution

One possible solution would be a onemkl::utility namespace with a routine to return the MAJOR, MINOR and PATCH numbers, e.g. version_number(major,minor,patch). With auto backend selection, the dispatcher would need to have its own version of the routine too.

I'm assuming all header files would be at the top level. If not, inconsistent versions would need to be considered there too. Providing a simple program to call these routines to check consistency would also be helpful.

@jasukhar jasukhar added the feature A request to add a new feature label Aug 3, 2020
@jasukhar
Copy link
Contributor

jasukhar commented Aug 3, 2020

Hi @edwards-nag ! Thanks for the proposal! That makes a lot of sense, we will plan to add this features.

@jasukhar jasukhar added the accepted The issue/feature is confirmed and going to be implemented label Aug 3, 2020
@ghost
Copy link
Author

ghost commented Aug 12, 2020

Thanks @jasukhar

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted The issue/feature is confirmed and going to be implemented feature A request to add a new feature
Projects
None yet
Development

No branches or pull requests

1 participant