Is there a way to establish the relationship between MKL build number (returned by mkl_get_version_string) and the version update number (a mapping table similar to the one existing for the compiler and found here: https://software.intel.com/en-us/articles/intel-compiler-and-composer-update-version-numbers-to-comp... ?
Also - what is the naming convention for versions and updates going forward? The latest is Intel MKL 2017; before it was 11.3 Update 4.
One version of product may has many build number, some of build numbers not open to external customer, only used for our internal testing & validation. You may know during the development of software product, there might be many progresses for testing and quality assurance. These build numbers are used for internal checking. Once we passed all testing, the final edition will be published with the latest build number. Thus, you could only find one build number for each published product. You may do not need to worry about the build number, you just need to provide version code when you submit any issue or problem to us.
For the naming of MKL, the latest one is MKL 2017, and further update version should be MKL 2017 update 1, MKL 2017 update 2....
Oliver, pls have a look at this KB article: https://software.intel.com/en-us/articles/which-version-of-the-intel-ipp-intel-mkl-and-intel-tbb-libraries-are-included-in-the-intel. This is not completed at this moment ( the latest MKL 2017 is not there ), but it may be usefiull for your purposes. we will update this soon.
ok, thanks for the answer. Yes Gennady I found this link but as you said it has not been updated yet.
The new naming convention MKL 2017 Update 1, etc.. seems fairly clear and consistent with the convention for the compiler.