- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Solved. I had a link to an local copy of lapack95.f90, an old "patch" to make MKL work.
Removing it fixes it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
![](/skins/images/7B0AB6865064EAE32B30EC9A4E94B48A/responsive_peak/images/icon_anonymous_message.png)
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page