Intel® oneAPI Math Kernel Library
Ask questions and share information with other developers who use Intel® Math Kernel Library.
7110 Discussions

mkl 10 error: not convinient for this processor

Ying_D_Intel
Employee
1,005 Views

I am trying mkl10 on em64t machines and goterror at run time:

MKL FATAL ERROR: SO k/kernel/source/xormrq_omp.fxx;mkl_lapack_zunmrq;323;333;; not convinient for this processor.

We linked libs from $MKLDIR/lib/em64t. (*_lp64.*)

Any idea what could cause the problem?

Thanks,

Ying

0 Kudos
11 Replies
TimP
Honored Contributor III
1,005 Views
The problem seems more likely to happen if you attempt to use the IA-64 libraries from /lib/64/. All /em64t/ and /32/ libraries should be compatible with em64t
0 Kudos
Ying_D_Intel
Employee
1,005 Views

I use lib/em64t on Intel Xeon machine.

libmkl_intel_thread.so and libpthread.so were also linked in. Not sure if that could be a problem?

Islibmkl_em64t.a required for em64t?

Thanks,

Ying

0 Kudos
TimP
Honored Contributor III
1,005 Views

Those libraries are normal. libmkl_thread requires also libguide or libiomp5.

libmkl_em64t.a in MKL 10 is a shortcut for libmkl_intel_lp64.a libmkl_thread.a libmkl_core.a. You should not try to link both .a and .so versions of any one library.
0 Kudos
Ying_D_Intel
Employee
1,005 Views

Thanks for your reply. Appreciate it.

I have mkl_lapack .a and .so linked in my program. Would this possibly be the reason of the error "not convenient for the processor"? but I have the same link line when I used mkl 9, which worked fine.

Or any other idea?

0 Kudos
TimP
Honored Contributor III
1,005 Views
Generally, it's risky to have more than one copy of the same library linked in. The MKL 10 documents specifically warn about the danger of that when using static libraries.
9.1 and 10 are significantly different in their library organization. Since mkl_lapack.a and .so in MKL 10 are not actually libraries, but are lists of 3 libraries, there is more opportunity to go wrong if you use those lists (scripts) and also link against a possibly conflicting library.

0 Kudos
Ying_D_Intel
Employee
1,005 Views

I am now using only libmkl_lapack.a in my program. But still have the same problem. What can I do to helpfurther investigate/debug the issue?

Thanks,

Ying

0 Kudos
Gennady_F_Intel
Moderator
1,005 Views

Could you show the linking line of  this example? Please check how do link this version properly vie MKL Linker Adviser: http://software.intel.com/en-us/articles/intel-mkl-link-line-advisor

a couples of  comments - version 10.0 is no longer supported. In the case if you will use 10.0 on the latest microarchitectures, then you will not get the all performance benefits from MKL's optimizations. 

--Gennady

0 Kudos
mecej4
Honored Contributor III
1,005 Views

Gennady,

You probably did not notice that the post that you responded to was from 2008! There seems to be a new problem with the forum software that is bringing old and stale posts, often from many years ago, to the top of the list. If anyone responds to the post without noticing the date, the thread becomes "active" and adds to the confusion.

0 Kudos
Gennady_F_Intel
Moderator
1,005 Views

You are right  - i didn't noticed that. Thanks a lot, mecej.  the thread is not active and the topic is not actual now.

0 Kudos
SergeyKostrov
Valued Contributor II
1,005 Views
>>...You probably did not notice that the post that you responded to was from 2008! There seems to be a new problem >>with the forum software that is bringing old and stale posts, often from many years ago, to the top of the list. If anyone >>responds to the post without noticing the date, the thread becomes "active" and adds to the confusion... The same problem happened with Intel C++ compiler and IPP forums. By some unknown reason lots of very old threads were marked as threads with New Posts. Did it happend because of some IDZ website maintenance activities?
0 Kudos
SergeyKostrov
Valued Contributor II
1,005 Views
Update and a note to a Moderator: >>>>...You probably did not notice that the post that you responded to was from 2008!.. >>... >>The same problem happened with Intel C++ compiler and IPP forums... I just verified and almost every IDZ forum is affected by that problem!
0 Kudos
Reply