| October 12, 2010 11:30 AM PDT | |
Reference Number : DPD200192258
Version : versions 10.2 Update 6 and 10.3 beta
Product : Intel(R) MKL
Operating System : all supported by Intel(R) MKL at this moment
Problem Description :
Version : versions 10.2 Update 6 and 10.3 beta
Product : Intel(R) MKL
Operating System : all supported by Intel(R) MKL at this moment
Problem Description :
The F90 DSS interface is broken because of currently DSS API supports Double Precision data types only.
Compilation DSS interfaces with Single Precision Data types will produces something like the following compilation errors
dss_sym_f90.f90(78): error #6633: The type of the actual argument differs from the type of the dummy argument. [VALUES]
dss_sym_f90.f90(82): error #6633: The type of the actual argument differs from the type of the dummy argument.
Compilation DSS interfaces with Single Precision Data types will produces something like the following compilation errors
dss_sym_f90.f90(78): error #6633: The type of the actual argument differs from the type of the dummy argument. [VALUES]
dss_sym_f90.f90(82): error #6633: The type of the actual argument differs from the type of the dummy argument.
[RHS]
dss_sym_f90.f90(82): error #6633: The type of the actual argument differs from the type of the dummy argument. [SOLUTION]
dss_sym_f90.f90(89): error #6633: The type of the actual argument differs from the type of the dummy argument. [STATOUT]
dss_sym_f90.f90(82): error #6633: The type of the actual argument differs from the type of the dummy argument. [SOLUTION]
dss_sym_f90.f90(89): error #6633: The type of the actual argument differs from the type of the dummy argument. [STATOUT]
Workaround:
As a temporarily workaround, we would recommend you to do the following:
1) make the call call DSS_CREATE( handle, MKL_DSS_SINGLE_PRECISION)
and then
2) manually change the API of these functions ( mkl_dss.f90 which is located in <mklroot\include> firectory ) by replacing REAL(KIND=8) by REAL(KIND=4) into those routines, which have been used into your application.
As an example, please see the MKL Forum tread, where the similar problem has been discussed.
Resolution Status :
fixed the next Update - 10.2 Update 7 and 10.3 Update 1
[DISCLAIMER: The information on this web site is intended for hardware system manufacturers and software developers. Intel does not warrant the accuracy, completeness or utility of any information on this site. Intel may make changes to the information or the site at any time without notice. Intel makes no commitment to update the information at this site. ALL INFORMATION PROVIDED ON THIS WEBSITE IS PROVIDED "as is" without any express, implied, or statutory warranty of any kind including but not limited to warranties of merchantability, non-infringement of intellectual property, or fitness for any particular purpose. Independent companies manufacture the third-party products that are mentioned on this site. Intel is not responsible for the quality or performance of third-party products and makes no representation or warranty regarding such products. The third-party supplier remains solely responsible for the design, manufacture, sale and functionality of its products. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. *Other names and brands may be claimed as the property of others.]
Do you need more help?
This article applies to: Intel® C++ Compiler for Linux* Knowledge Base, Intel® C++ Compiler for Mac OS X* Knowledge Base, Intel® C++ Compiler for Windows* Knowledge Base, Intel® Cluster Toolkit for Linux* Knowledge Base, Intel® Cluster Toolkit for Windows* Knowledge Base, Intel® Fortran Compiler for Linux* Knowledge Base, Intel® Fortran Compiler for Mac OS X* Knowledge Base, Intel® Math Kernel Library Knowledge Base
For more complete information about compiler optimizations, see our Optimization Notice.
Comments (0) 
Trackbacks (0)
Leave a comment 
To obtain technical support, please go to Software Support.

