https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Error-compiling-Intel-mkl-scalapack-example-pcdbdriver/m-p/763437#M74 The code is from the "bad old days" of Fortran. It was common to pass around uninitialized "work arrays" with no regard to their declared type, because dynamic allocation did not exist. With separate compilation or no argument checking, it will work fine as long as the byte-size of the array is large enough and passed correctly.<BR /><BR />There are myriad combinations of compiler switches, Scalapack, Blacs, MPI and MKL libraries that can be used when running the test problems provided with MKL. You should specify which combination you used, since there are too many to try otherwise.<BR /><BR />With release 066, which is what I have access to, file pcdbinfo.f does not contain any variable called MEM. However, the 26th argument is the integer array WORK, which corresponds to the actual argument MEM in pcdbdriver.f, which itself is in ...TESTING\LIN, not ...TESTING\EIG as you stated.<BR /><BR />Instead of using the makefile, I simply compiled the files<BR /><BR /> pcdbdriver.f <BR /> pcdbinfo.f<BR /> pcmatgen.f<BR /> pcbmatgen.f <BR /> pcdblaschk.f<BR /> pcdbmv1.f <BR /> pmatgeninc.f<BR /><BR />and linked with the libraries<BR /><BR /> mkl_scalapack_core_dll.lib <BR /> mkl_blacs_dll.lib <BR /> mkl_intel_c_dll.lib <BR /> mkl_sequential_dll.lib<BR /><BR />and ran the resulting .exe file with the provided data file BLU.DAT. The results looked plausible:<BR /><PRE>[bash]...<BR />Finished 12 tests, with the following results:<BR /> 6 tests completed and passed residual checks.<BR /> 0 tests completed and failed residual checks.<BR /> 6 tests skipped because of illegal input values.[/bash]</PRE> Fri, 13 Aug 2010 14:35:37 GMT mecej4 2010-08-13T14:35:37Z https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Error-compiling-Intel-mkl-scalapack-example-pcdbdriver/m-p/763436#M73 Dear All,<BR />I am using Intel fortran 11.1 intergrated with VS 2008. I am trying to run scalapack example pcdbdriver given in Intel\\Compiler\\11.1\\060\\mkl\\tests\\scalapack\\source\\TESTING\\EIG folder. When I tried to compile it I had compiler error saying "The type of the actual argument differs from the type of the dummy argument. [MEM] ". I did notice that in pcdbdriver source file Mem is defined as complex in pcdbdriver.f and as integer in pcdbinfo.f <BR />Is this just a mistake or am I missing something.<BR />Regards,<BR />newbie2scalapack Fri, 13 Aug 2010 02:21:29 GMT https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Error-compiling-Intel-mkl-scalapack-example-pcdbdriver/m-p/763436#M73 skravoof 2010-08-13T02:21:29Z https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Error-compiling-Intel-mkl-scalapack-example-pcdbdriver/m-p/763437#M74 The code is from the "bad old days" of Fortran. It was common to pass around uninitialized "work arrays" with no regard to their declared type, because dynamic allocation did not exist. With separate compilation or no argument checking, it will work fine as long as the byte-size of the array is large enough and passed correctly.<BR /><BR />There are myriad combinations of compiler switches, Scalapack, Blacs, MPI and MKL libraries that can be used when running the test problems provided with MKL. You should specify which combination you used, since there are too many to try otherwise.<BR /><BR />With release 066, which is what I have access to, file pcdbinfo.f does not contain any variable called MEM. However, the 26th argument is the integer array WORK, which corresponds to the actual argument MEM in pcdbdriver.f, which itself is in ...TESTING\LIN, not ...TESTING\EIG as you stated.<BR /><BR />Instead of using the makefile, I simply compiled the files<BR /><BR /> pcdbdriver.f <BR /> pcdbinfo.f<BR /> pcmatgen.f<BR /> pcbmatgen.f <BR /> pcdblaschk.f<BR /> pcdbmv1.f <BR /> pmatgeninc.f<BR /><BR />and linked with the libraries<BR /><BR /> mkl_scalapack_core_dll.lib <BR /> mkl_blacs_dll.lib <BR /> mkl_intel_c_dll.lib <BR /> mkl_sequential_dll.lib<BR /><BR />and ran the resulting .exe file with the provided data file BLU.DAT. The results looked plausible:<BR /><PRE>[bash]...<BR />Finished 12 tests, with the following results:<BR /> 6 tests completed and passed residual checks.<BR /> 0 tests completed and failed residual checks.<BR /> 6 tests skipped because of illegal input values.[/bash]</PRE> Fri, 13 Aug 2010 14:35:37 GMT https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Error-compiling-Intel-mkl-scalapack-example-pcdbdriver/m-p/763437#M74 mecej4 2010-08-13T14:35:37Z