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

[RFC|oneMKL]Enable programmatic versioning #561

Merged
merged 20 commits into from
Sep 30, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Remove top-level version macro
vmalia committed Sep 30, 2024
commit 8916f19d53294e0bf7cb4e732d63ea1a163078c9
17 changes: 6 additions & 11 deletions doc/versioning.rst
akukanov marked this conversation as resolved.
Show resolved Hide resolved
Original file line number Diff line number Diff line change
@@ -96,22 +96,17 @@ Example
| oneAPI 1.2 rev 1 will be represented as a numerical value of 10201
| oneAPI 1.2 rev 2 will be represented as a numerical value of 10202

The implementation is required to define a macro with the numerical value
of the specification version. The macro name should be `ONEAPI_SPEC_VERSION`
and the value should be the numerical value of the specification version.
The components within the specification can implement their own macro
with the numerical value of the specification version. The macro name should be
`<COMPONENT>_SPEC_VERSION` and the value should be the numerical value
of the specification version.
The implementation must define a macro with its name following the scheme,
`<COMPONENT>_SPEC_VERSION` and having the numerical value of the specification
version, for each component.

Example

.. code-block:: c

#define ONEAPI_SPEC_VERSION 10101
#define ONETBB_SPEC_VERSION ONEAPI_SPEC_VERSION
#define ONEMKL_SPEC_VERSION ONEAPI_SPEC_VERSION
#define ONETBB_SPEC_VERSION 10201
#define ONEMKL_SPEC_VERSION 10101


[1] MINOR and REVISION values are limited to double digits to allow programmatic
[1] MINOR and REVISION values are limited to double digits to allow numerical
comparison of versions.