topic There is no matching specific subroutine for this generic subroutine call: oneAPI seems more fussy in Intel® oneAPI Math Kernel Library

There is no matching specific subroutine for this generic subroutine call: oneAPI seems more fussy

Peter0000 — Thu, 08 Sep 2022 11:48:23 GMT

In compiling some old code, I find oneAPI iFort is much stricter about interfaces e.g

error #6285: There is no matching specific subroutine for this generic subroutine call. [GETRF]

USE F95_PRECISION

USE LAPACK95

etc

REAL(DP) :: M(ng,ng)

INTEGER [,TARGET] :: indx(ng)

INTEGER :: info

etc

call GETRF(M,indx,info)

While many were fixed by simply changing "info" from INTEGER I4B (my past error) to INTEGER, the above was not fixed.

Adding TARGET to indx did not help

Re: There is no matching specific subroutine for this generic subroutine call: oneAPI seems more fus

Peter0000 — Thu, 08 Sep 2022 15:19:26 GMT

My apologies. While I have not found put why my legacy code fails to compile, my attempts to replicate it the fault fail. It does not even care if TARGET is present.

o the attached works

I may leave the question open in case I learn anything when or if I find my issue.

Re: There is no matching specific subroutine for this generic subroutine call: oneAPI seems more fus

Peter0000 — Thu, 08 Sep 2022 16:59:40 GMT

Solved. I had a link to an local copy of lapack95.f90, an old "patch" to make MKL work.

Removing it fixes it.

Re:There is no matching specific subroutine for this generic subroutine call: oneAPI seems more fussy

SantoshY_Intel — Fri, 09 Sep 2022 06:08:00 GMT

Hi,

Thank you for posting in Intel Communities.

Glad to know that your issue is resolved. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel.

Thanks & Regards,

Santosh