Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29280 Discussions

Calling LAPACK library Directly from C#

Ngu_Soon_Hui
Beginner
‎11-30-2010 01:04 AM
1,160 Views
I understand that I can call fortran function in DLL from C# by using PInvoke. Now I want to call LAPACK function such as degmv., but I don't want to write a wrapper fortran code on top of that.
How to call LAPACK library directly from C#?
0 Kudos

Link Copied

2 Replies
Steven_L_Intel1
Employee
‎11-30-2010 09:59 AM
1,160 Views
Copying a response from a private reply:

"dgemv isn't an lapack function, it's a BLAS function. If built from public source, it is a Fortran77 subroutine, if modified or closed source, it still should preserve Fortran interoperability. Intel MKL lapack and BLAS functions provided with recent ifort come with C prototypes (not all strictly correct), in case that helps. I don't see what you expect to change by putting a Fortran wrapper over a Fortran callable subroutine. If you want to patch over some legacy style interface questions, you could take the public source code and modify it to USE iso_c_binding, or you could accomplish that in a wrapper."
0 Kudos
Copy link
Ngu_Soon_Hui
Beginner
‎11-30-2010 07:50 PM
1,160 Views
Hello,
are you saying that I would have to build the BLAS library myself, that MKL doesn't come with a binary dll of the BLAS library?
From my digging this seems to be the case for BLAS . FOR LAPACK, there is a binary version of mkl_lapack.dll, though. Why this double standard?
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.