Intel® Visual Fortran Compiler for Windows*

Access 2D Fortran array from C - odd behaviour

This topic must have been beaten to death, but the issue I've encountered seems very odd.

Here is the C code:

void test_array(int *, int *, double **); // To test accessing a Fortran 2D array.

void test_get_array()

{
    int i;
    int narr1, narr2;
    double *farr;
    test_array(&narr1, &narr2, &farr);
    for (i=0;i<narr1*narr2; i++)
        printf("%d %f\n",i,farr[i]);
}

 

and the Fortran:

Reference Material for Visual Fortran Windowing Applications

Hello,

I am attempting to create a simple windowing application in Fortran using Visual Studio.  I have experience with C and BASIC, but I am completely new to Fortran.  In order to create my application, I have started off by attempting to reverse engineer the sample SDI code, and so far it has done a great deal to familiarize me with the nuances of this language.

Linking IVF Compiled DLL to Qt Application

Hi everybody,
This is my first attempt at library assembly, so please have mercy! Let me also start by saying to Steve Lionel: Wow, you answer a lot, I hope they are paying you well there at Intel!

I am trying to link an external library (written in .f90 and compiled with IVF on VS2012) to my Qt application (32bit based on Qt 5.5.0- MinGW 4.9.2).

I have a few questions:

Multithreaded vs Multithread DLL

     The following problem, involving "Multithreaded" vs. "Multithread Dll" Runtime Libraries, is not critical to anything I'm doing, but my curiosity is aroused.
     The program is written in .f90 code developed and compiled with MSVS Professional 2013 with Intel Parallel Studio XE 2015 Update 4 Composer Edition For Fortran Windows*. It "USE's":lapack95, OMP_LIB and two homemade MODULE's.

Polymorphic dummy arguments and ICE

This discussion is going to be generic until I can create a suitable small test case.  I am just hoping somebody has seen this problem before and can point me in the right direction.

I am attempting to create a TYPE and a TYPE which extends the original.  I then wish to use the second (child class) in many places around my fixed-form Fortran code.  I have been getting the warning message 

warning #8499: The procedure has a dummy argument that is polymorphic. Required explicit interface is missing from original source.

DLLEXPORT and unresolved external reference

I'm compiling a fortran DLL project. I have two subroutines in the same .f file. The first one shown below calls the second one, but I'm getting unresolved external symbol. The problem must be how I'm exporting them so they can be called from Excel VBA.

I have iface set to Default for this project.
The unresolved error goes away if I remove the !DEC statement from SUBB, but I need it.
All the argument variables are numeric except for the one called rtn.

What the heck am I doing wrong?!@#$

LNK2019 error

I am in the process of converting from Compaq Visual Fortran to Intel Visual Fortran. 

I am trying to run simple "hello_world" program.

My program complies just fine with:   "Ifort /c hello_world.f90"

However, when I link with "Ifort /exe:runmodel.exe hello_world.obj"

I get the following error messages

Array of EXTERNAL

In the manual I found:

EXTERNAL FACET
CALL BAR(FACET)
SUBROUTINE BAR(F)
EXTERNAL F
CALL F(2)

I would like something as:

SUBROUTINE BAR(F,t,y)
EXTERNAL, DIMENSION(1:2) :: F
EXTERNAL fun
fun = F(1)
CALL fun(t,y)
fun = F(2)
CALL fun(t,y)

and

f(1) = myode
f(2) = myresult

SUBROUTINE myode(t,y)
! do something
END

SUBROUTINE myresult(t,y)
! do something
END

Do you think it is possibile?

 

Assine o Intel® Visual Fortran Compiler for Windows*