The comments on lines 229 through 235 show how the order of the USE statements determine if the code compiles or not. I have attached an example that should compile, and there are several ways to work around the bug. ****** The second problem is that, i have the same result for different time that i print the solution. !Next step Write result in the file, for different time !Once done i will use F1 as the initial condition for the second equation !Compute the solution of the first equationĬall tridag( A,B,C,F0, F1, N) !F0 is a two dimensional function, F1, a one dimensional function What i did to overcome this is the following (just a example): The first one is that the coefficients use in tridag are 2 D array while this routine use 1 D array. For this i have to solve linear systems of equation using tridag (fortran ) routine. I'm trying to solve a problem use time splitting method.

TYPE(TT) :: ARG ! This will trigger an error at run time. However, ror the case that fails, shouldn't the compiler detect the (incorrect?) use of TYPE instead of CLASS on line 39 though? MODULE M1 Now, if you toggle lines 39 and 40, the code runs as expected. The code below, as is, will compile and create the following error at runtime: 'forrtl: severe (173): A pointer passed to DEALLOCATE points to an object that cannot be deallocated' What do I need to do to make my code compliant with XE2017? I have used this technique 100's of tmes in my application, so changing this is going to be a major job. Write(*,*) 'Function not found: '//TRIM(NAME)ĬALL C_F_PROCPOINTER(TRANSFER(p_USERFUNC, C_NULL_FUNPTR), DragCoeff_F)ĬALL DragCoeff_F(Reynolds, Sphericity, Value, Units) P_USERFUNC = getprocaddress(hModule=dll_handle, lpProcName=TRIM(NAME)//C_NULL_CHAR) PROCEDURE(DragCoeff_int), pointer :: DragCoeff_F Real(KIND=KIND(0D0)), INTENT(OUT), DIMENSION(1) :: ValueĬharacter(LEN=20), INTENT(INOUT) :: Units Real(KIND=KIND(0D0)), INTENT(IN), DIMENSION(1) :: Reynolds, Sphericity !DEC$ ATTRIBUTES STDCALL, ALIAS:'DragCoeff_int' :: DragCoeff_int Subroutine DragCoeff_int(Reynolds, Sphericity, Value, Units) In XE2016, this code works for me, so that I can then load and call the relevant function out of a DLL: I am struggling a bit to understand this behavior. However, the alternate lines (with simultaneous use of PASS, or nothing for both PROCEDURE statements) compile ok. The code below does not compile: the error returned by the compiler is 'error #8383: The dummy arguments of an overriding and overridden binding that correspond by position must have the same characteristics, except for the type of the passed object dummy arguments.

Intel visual fortran compiler torrent