We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A provisional version 1.4 of oneAPI Specification was created a few days back.
The sparse BLAS domain in oneMKL specification was overhauled and rewritten (no backward compatibility whatsoever) in June 2024 in #522
Shouldn't this trigger a major-version update of the oneAPI Specification to 2.0 instead of 1.4?
Tagging: @rscohn2, @spencerpatty, @Rbiessy, @sknepper, @mkrainiuk, @vmalia
The text was updated successfully, but these errors were encountered:
Components can choose to have their own version. onemkl can declare that the next version is 2.x or 2025.x
In hindsight, I would have used calendar versioning for the combined document.
Sorry, something went wrong.
rscohn2
No branches or pull requests
A provisional version 1.4 of oneAPI Specification was created a few days back.
The sparse BLAS domain in oneMKL specification was overhauled and rewritten (no backward compatibility whatsoever) in June 2024 in #522
Shouldn't this trigger a major-version update of the oneAPI Specification to 2.0 instead of 1.4?
Tagging: @rscohn2, @spencerpatty, @Rbiessy, @sknepper, @mkrainiuk, @vmalia
The text was updated successfully, but these errors were encountered: