I am using Visual Studio 2010. Every time I type in a parentheses the program slows down for literally 20 seconds and then goes back to normal again. I've already fiddled around with the Tools>Options>Text Editor>Fortran>Advanced options but could not pinpoint which option is triggering this behavior.

Well, there is no way I am going to avoid typing in parentheses when coding and this behavior is extremely frustrating and messing with my workflow. How do I deactivate this? I don't want any fancy code-checking options. I just want to code without the whole damn thing freezing every so often.

Hi,

I have been encountering some inconsistent results when calling zheev() from a program I am attempting to parallelize with MPI. Zheev(), which calculates eigenvectors/values of a complex 2D Hermitian matrix, returns eigenvalues in an array that are very comparable between serial and parallel versions (only off by about 13-8). However, the eigenvectors it returns can vary considerably and strangely; some elements will have an imaginary or real part that is reasonably close, while the other is nonsensical, or both parts of the element could be quite different. I created a small test case (that just reads the matrix from a file) to illustrate my issue that exhibits this issue:

program zheevtest_serial
   implicit none
   double complex, allocatable :: matrix (:,:), work(:)
   integer :: msize, i, j, lwork, info
   double precision, allocatable :: rwork(:), eigv(:)

   open(7,file='pre-zheev_mat_ser.dat')
   read(7,*) msize

   allocate(matrix(msize,msize))
   allocate(eigv(msize))
   allocate(work(msize*msize))
   allocate(rwork(3*msize-2))
   lwork = msize*msize

   do i=1,msize
     do j=1,msize
       read(7,*) matrix(j,i)
     enddo
   enddo
   close(7)

   call zheev('N','U',msize,matrix,msize,eigv,work,-1,rwork,info)
   lwork = work(1)

   call zheev('V','U',msize,matrix,msize,eigv,work,lwork,rwork,info)

   open(8,file='out_ser.dat')
   write(8,*) matrix
   close(8)

end program zheevtest_serial

The MPI parallelized version of this test case differs only where each process writes to a different file at the end, and the usual MPI setup calls.

This discrepancy exists between serial and MPI with >1 processor (1 processor gives identical results to serial). I am using the modules fftw/3.3.0-intel-openmpi, openmpi/1.4.4-intel-v12.1, and intel/15.0.1 to compile, with flags -xHost and -mkl.

I've attached the matrix if anyone would like to try and replicate this issue. If anyone could give me some insight as to what might be going on, or just more detail as to how zheev() operates, that would be greatly appreciated.

-Duncan

Dear all,

I am trying to write CMakeLists.txt to let CMake to generate C++ and Fortran projects. Because I need to build both static and dynamic libraries, I need to build objects at first, and then link them to static and dynamic libraries. The CMake code to generate projects is as follows:

Code to generate static library by 'OBJECT' keyword of CMake:

	ADD_LIBRARY(MUMPS_d_FORTRAN OBJECT"${MUMPS_COMMON_OTHER_HEAD}""${dMUMPS_SRC}""${dMUMPS_OTHER_SRC}")

	SET_TARGET_PROPERTIES(MUMPS_d_FORTRAN PROPERTIES
							COMPILE_FLAGS "${GENERIC_COMPILER_FLAGS_FORTRAN} ${ORDERINGS_COMPILER_FLAGS_FORTRAN} -c"
							LINKER_LANGUAGE FORTRAN)

	TARGET_INCLUDE_DIRECTORIES(MUMPS_d_FORTRAN PUBLIC
							"${MUMPS_INCLUDE_DIRS}""${LIBSEQ_INCLUDE_DIRS}")

code to generate static library by objects:

		ADD_LIBRARY(dmumps STATIC
								$<TARGET_OBJECTS:MUMPS_d_FORTRAN>)
		SET_TARGET_PROPERTIES(dmumps PROPERTIES
								COMPILE_FLAGS "${GENERIC_COMPILER_FLAGS_FORTRAN} ${ORDERINGS_COMPILER_FLAGS_FORTRAN} -c"
								LINKER_LANGUAGE C)

		TARGET_INCLUDE_DIRECTORIES("dmumps" PUBLIC"${MUMPS_INCLUDE_DIRS}""${LIBSEQ_INCLUDE_DIRS}")

Now the problem is that when I build the whole solution, the project 'MUMPS_d_FORTRAN' can successfully generate MUMPS_d_FORTRAN.lib but the project 'dmumps' generated nothing. What could lead to this problem.

I tested both VS2013 + Intel Parallel Studio 2016 update 2 and VS2015 + Intel Parallel Studio 2017 update 4 and the results are the same.

PS: I have similar operation for C++ project, but both projects can successfully generate static libraries.

Thanks,

Tang Laoya

Hi,

I'm trying to configure a project using cmake 3.9 on x64 target. I use visual studio 2015 and the last intel fortran version.

During the configuration process cmake tries to compile the attached file but compilation failed with Unspecified error. 

Any idea ?

Regards

Recoding an VERY old piece of software (originally vector for a CRAY XMP) to run faster on my PC.  The following code is typical of some limiting sequences:

               DO j = 1, nelem
                  W(j) = zero
                  DO i = 1, nfmaxp2
                     IF ( CN(i,j)>0 ) W(j) = W(j) + A(i,j)*u(CN(i,j))
                  ENDDO
               ENDDO

Problem is the IF statement and I've tried server variations to speed things up but no real progress.  Thought the brain truss here might have some suggestions.

Note: The original code on a particular test case ran 35+hrs on the CRAY.  Today on my Haswell CPU PC running 8 threads and using the latest Intel Fortran compiler it takes 6+ minutes but there is still room for improvement.

My old project making trouble again!

fortcom: Fatal: There has been an internal compiler error (C0000005).

After update to VS2107 and IVF2017(update4, w_comp_lib_2017.4.210), there is an internal compiler error. I have tried to make the question more clear by cutting try the codes. Finally I could repeat the error by some brief code and compiler option. But I don't know if it is a general case, after all people around won't update the compiler as often as I..

My simple code as below. And the error only occur in debug configure by set 'Debug information format' to Full (/debug:full), and 'Inforamtion for parameter constant' to All (/debug-parameters:all).

There is no problem with IVF2015 and some early versions I have in hand.

module M


implicit none


character(LEN=40), public, parameter :: Name = "Name"
 
contains
  
subroutine foo1 ()
implicit none
    call foo2(Name)
end SUBROUTINE

end module

I am trying to run an OpenMP Fortran code using Intel Fortran. 

At the beginning of my code I allocate 7 very large matrices:

    ! Allocate
    REAL, ALLOCATABLE :: m1(:,:,:,:,:,:,:,:,:)
    REAL, ALLOCATABLE :: m2(:,:,:,:,:,:,:,:,:)
    REAL, ALLOCATABLE :: m3(:,:,:,:,:,:,:,:,:)
    REAL, ALLOCATABLE :: m4(:,:,:,:,:,:,:,:,:)
    REAL, ALLOCATABLE :: m5(:,:,:,:,:,:,:,:,:)
    REAL, ALLOCATABLE :: m6(:,:,:,:,:,:,:,:,:)
    REAL, ALLOCATABLE :: m7(:,:,:,:,:,:,:,:,:)

    ALLOCATE(m1(2,161,20,2,2,21,30,2,2))
    ALLOCATE(m2(2,161,20,2,2,21,30,2,2))
    ALLOCATE(m3(2,161,20,2,2,21,30,2,2))
    ALLOCATE(m4(2,161,20,2,2,21,30,2,2))
    ALLOCATE(m5(2,161,20,2,2,21,30,2,2))
    ALLOCATE(m6(1,161,20,2,2,21,30,2,2))
    ALLOCATE(m7(1,161,20,2,2,21,30,2,2))   

I then run a code with a big parallelized loop. 

    !$omp parallel do default(private) shared(m1, m2, m3, m4, m5, m7,  someothervariables)

Some of the matrices `m1` to `m7` are indeed used in subroutines, which might lead to creation of temporary arrays. 
In any case the code runs fine if done serially. But it crashes with the following error if run with openMP regardless of the number of cores I am using:

The machine I am using has `128GB` of ram. Not sure if this is the limiting factor or not. If I decrease the last index of each matrix to 1, the code runs fine in 24 cores. Given that I am increasing the size of the memory used by 2, it should run in 12 cores, at least no? 

Maybe I am doing some big error, or perhaps is just some Fortran option that needs to be changed ...

VS2017 + IVF2017(update4, w_comp_lib_2017.4.210)

I found if 'preprocess source file' is set to Yes, the compile error shown in output window seems a little strange: '\' before the source file name will become '/', which will cause a little inconvenient for VS to open the file by double click the error message line when the file is already opened.

PreprocessYes: '......\Console1/Source1.f90(3): error #5082: Syntax error......'.

PreprocessNo : '......\Console1\Source1.f90(3): error #5082: Syntax error......'.

The early versions I have(VS2010 + IVF2015/2012) does not have that feature.

Is it designed to? I do not think it reasonable.

Hello,

I have a problem I would like to solve but somehow I struggle.

I have different types defined:

! Type KUGS ([KUG]el [S]cheibe)
	TYPE, PUBLIC :: typeKUGS
		CHARACTER(4) :: cIdent	= 'KUGS'
		CHARACTER(4) :: cANam	= ''
		CHARACTER(4) :: cMant	= ''
		CHARACTER(4) :: cMat	= ''
		CHARACTER(4) :: cSpaw	= ''
		TYPE(typeKOOS) :: KOOS_P1, KOOS_P2
		REAL(8) :: rR1 = -1._dp, rR2 = -1._dp
		REAL(8) :: rS1 = -1._dp, rS2 = -1._dp
		REAL(8) :: rRKug

		CONTAINS
			PROCEDURE, PUBLIC::setKUGS => setKUGS_sub
	END TYPE typeKUGS

	! Type TORS ([TOR]us [S]cheibe)
	TYPE, PUBLIC :: typeTORS
		CHARACTER(4) :: cIdent	= 'TORS'
		CHARACTER(4) :: cANam	= ''
		CHARACTER(4) :: cMant	= ''
		CHARACTER(4) :: cMat	= ''
		CHARACTER(4) :: cSpaw	= ''
		TYPE(typeKOOS) :: KOOS_P1, KOOS_P2
		REAL(8) :: rR1 = -1._dp, rR2 = -1._dp
		REAL(8) :: rS1 = -1._dp, rS2 = -1._dp
		REAL(8) :: rRtor

		CONTAINS
			PROCEDURE, PUBLIC::setTORS => setTORS_sub
		END TYPE typeTORS

Now I want to define the type typeVAM1 which should have a pointer pointing to a typeKUGS, typeTORS or some other type, but from what I know a pointer always have to be of the same variable type as the target

! Type VAM1
		TYPE, PUBLIC :: typeVAM1
			CHARACTER(4) :: cIdent	= 'VAM1'
			CHARACTER(4) :: cVNam	= ''
			CHARACTER(1) :: cVTyp	= ''
			CHARACTER(1) :: cMIA	= ''
			CHARACTER(4) :: cVA		= ''
			CHARACTER(4) :: cPA		= ''
			CHARACTER(4) :: cMV		= ''
			CHARACTER(4) :: cVTNa	= ''
			REAL(8) :: rFBAln		= -1._dp
			REAL(8) :: rFBAls		= -1._dp
			REAL(8) :: rEckD		= 0._dp
			REAL(8) :: rArov		= -1._dp
			REAL(8) :: rSFak		= -1._dp
			VOID, POINTER :: pKVNa	! this should point to typeKUGS or typeTORS etc...
			REAL(8) :: rAriv		= 0._dp
			INTEGER :: iMaNv		= 0

		CONTAINS
			PROCEDURE, PUBLIC::setVAM1 => setVAM1_sub
		END TYPE typeVAM1

Does someting like a void pointer exist or someone has an other idea to solve this?

Dear all,

I encounter these errors:

error LNK2001: unresolved external symbol __intel_cpu_feature_indicator

error LNK2001: unresolved external symbol __intel_cpu_feature_indicator_x

error LNK2001: unresolved external symbol __intel_cpu_features_init

I tried using both -NODEFAULTLIB and linking directly to the static libraries I used (including MKL libraries) and without -NODEFAULTLIB. 

I am using Microsoft Visual Studio 2017 and Intel Parallel Studio XE 2017.

Many thanks,

Tudor Cretu

I have a question: Is the Intel Parallel Studio XE Composer Edition for Fortran or
Intel Visual Fortran Studio XE for Windows OS works with Intel MPI 5.1 Library?

I have been using VS 2010 and Intel Fortran 2013 SP1.  My project uses both languages and works fine.

Today I upgraded to VS 2015, and when I try to open the .sln file it fails.  Here is what it says:

Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
     - SYNOPSYS200_lib_, "C:\SYNOPSYSV15\SYNOPSYS200_lib_.vfproj"

No changes required
These projects can be opened in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without changing them.
     - SYNOPSYS200, "C:\SYNOPSYSV15\SYNOPSYS200.sln"

I looked at the Migration Report, and it was no help.  What should I do?

I have different Fortran projects. If I want to use some of these projects in my new project, I have to change that projects in the format of modules, subroutines, functions or dll files and include them as part of my new project which is time consuming. Please let me know if there is any possibility to put all these projects in a solution file and call a project when I need it.

If there is such a possibility, please let me know if it is also possible to send data from one project to another project.

For example, I have a project that open a file and read a matrix in that file and invert it. I want to use this project in my new project without changing it to the module, subroutine, function or dll file. If there is possibility to use that project in my new project, please also let me know if it is possible to send the matrix directly to the project which invert it instead of writing the matrix in a file. 

Hi,

I have a simple program in fortran 77 that I want to pass dynamic array size between the program and the subroutine.

But I encountered a problem with the compiling

the code is as below

            program read_sub
! ********************** Main program *********************************
      implicit none

      integer :: cm(30),n,i,nstress
      integer,allocatable,dimension(:),pointer :: stress
      n=30

      nstress=size(cm)
      allocate stress(nstress)

      do i=1,n
          cm(i)=10
      enddo

      CALL umat(cm,stress,n,nstress)

      end program read_sub


	  subroutine umat(cm,stress,n,nstress)
      integer :: cm(30),n,i,nstress
      integer :: stress(nstress)

      do i=1,nstress
          stress(i)=cm(i)+10
      write(*,*) stress(i)
      enddo

      end

I think allocate and size doesn't work with fortran 77 but I am not sure.

Any help will be appreciated

Hello!

I am pretty new to Fortran and fail since a few days to a initial problem.
I am not able to bring data given by a xml file to my Fortran program.(Matrices)

I have data provided in an XML file. 
It is structured something like:

<FIELDNAME>
    <ROWS>?</ROWS>
    <COLS>?</COLS>
    <DATA>?</DATA>
</FIELDNAME>
...then comes the next <FIELDNAME> ... ... ... ? represents a double(kind=8)

I have written a parser in vb.net and now i am able to create a *.dat file in every way i like it.
My newest attempt is simply structured like:

FIELDNAME as character(10)
NUMBER OF ROWS as character(10)
NUMBER OF COLUMNS as character(10)
?(1,1)
?(2,1)
... ... ... till the next FIELDNAME ... ... ... ? represents a double(kind=8)

In the file it looks like:

MATRIX1
3.0
3.0
1.0E-18
2.0
3
4.0E+5
5.0
6.0
7.0
8.0
9.0
MATRIX2
...
...
...

The FIELDNAMEs are always the same ~30 Fieldnames in the same order containing Martices.

I thought it would be easy to bring the data into my program cause i can format it as i wish in vb.net but i fail. I also fail when i try to do it with vb.net and try to pass the arrays to fortran as such(I don't want to do it this way anymore cause all description i found in the internet are done like kidding me.) Using FoX compiled under VisualStudio to read from the input.xml itself also was not possible. I've wastet several days to this.
 

Has someone an Code example or something similar for me how this, in this case "initial step" can be done?

I would be very glad if someone could help me!

I need to be able to compile and link from the command line instead of Visual Studio. I read discussion in this topic to learn how to do that. I thus rebuilt one of the configurations (Release for x64) in Visual Studio (Community 2015, Update 3) with IPS XE 2017 Update 2 and then changed the BuildLog.htm file to a .bat file with the following contents:

Rc /fo "x64\Release/Resources.res""D:\Test\Resources.rc"

set compiler_options=/nologo /MP /O2 /fpp /I"%MKLROOT%" /I"\include" /fixed /extend_source:132 /Qopenmp /fpscomp:general /Qdiag-disable:8290,8291,5462 /warn:declarations /warn:unused /warn:truncated_source /warn:noalignments /warn:interfaces /assume:byterecl /module:"x64\Release\\" /object:"x64\Release\\" /Fd"x64\Release\vc140.pdb" /libs:static /threads /Qmkl:parallel /c /Qlocation,link,"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\\bin\amd64" /Qm64

ifort %compiler_options% MyApp.for

set linker_options=/OUT:"x64\Release\MyApp.exe" /INCREMENTAL:NO /NOLOGO /DELAYLOAD:"MyAppx64.dll" /MANIFEST /MANIFESTFILE:"x64\Release\MyApp.exe.intermediate.manifest" /MANIFESTUAC:"level='asInvoker' uiAccess='false'" /SUBSYSTEM:CONSOLE /STACK:100000000 /IMPLIB:"D:\Test\x64\Release\MyApp.lib" delayimp.lib ..\DLL\x64\GFMx64.lib mkl_intel_lp64_dll.lib mkl_intel_thread_dll.lib mkl_core_dll.lib libiomp5md.lib -qm64 /qoffload-ldopts="-mkl=parallel"

Link %linker_options% "x64\Release\MyApp.obj""x64\Release/Resources.res"

mt.exe /nologo /outputresource:"D:\Test\x64\Release\MyApp.exe;#1" /manifest "x64\Release\MyApp.exe.intermediate.manifest"

The resulting executable has the same size like the one created by Visual Studio, so I assume everything is OK. What is confusing are two warnings during the linking phase:

LINK : warning LNK4044: unrecognized option '/qm64'; ignored
LINK : warning LNK4044: unrecognized option '/qoffload-ldopts=-mkl=parallel'; ignored

Why are these two options included in the linking command in BuildLog.htm when they are reported unrecognized on the command line?

Also, are all the compiler and linker options listed above needed when the command line is used?

am running a visual studio 2015 > intel visual Fortran compiler > console application project .so I added these files. I want to get DLLs and call them from somewhere else.(maybe I must use another type of visual Fortran compiler projects, I am not sure)

I only make an empty consol application of visual Fortran compiler ,then add my .f90 Fortran files.and then run the project.so I got errors.maybe another routine must be done.

alloc_after_mesh.f90 arint3D.f90
baric.f90 blomamor.f90 blomamorc.f90 blomamorp.f90
bloseg3D.f90 bloseg3Dc.f90 calindc.f90 calprebloqueo.f90
calvnoru.f90 cg.f90 cgrevcom.f90 comprobaciones.f90
conlud.f90 creamake.dat derff.f90 ef_el.f90
electrostatica3D.f90 endat3D.f90 ensacmor.f90 funciones3D.f90
gauspp.f90 leema3D.f90 leetmp.f90 Makefile
Makefile.windows matlap_orto.f90 matriz3D_orto.f90 matvec.f90
modulos_electros3D.f90 mod_mcambio.f90 norl2_3D.f90 [object]
principal.f90 procb1.f90 procb2.f90 psolve.f90
punto1.f90 readxml.f90 reslud.f90 semi3D.f90
stoptest2.f90 wrtcmp.f90 wrtcmpv.f90
but when compiling I got these errors:

error code 23 (returned by OpenValidateX) Compilation Aborted (code 1) error #7002: Error in opening the compiled module and so far...

Severity Code Description Project File Line
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\semi3D.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\alloc_after_mesh.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\arint3D.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\baric.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\blomamor.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\blomamorc.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\blomamorp.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\bloseg3D.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\bloseg3Dc.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\calindc.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\calprebloqueo.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\calvnoru.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\cg.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\cgrevcom.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\comprobaciones.f90 1
Error Compilation Aborted (code 1) C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\comprobaciones.f90 1
Error error #7002: Error in opening the compiled module file. Check INCLUDE paths. [MESH] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\comprobaciones.f90 7
Error error #6404: This name does not have a type, and must have an explicit type. [MESH_READ_ARRAY_UNFORMATTED] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\comprobaciones.f90 203
Error error #6404: This name does not have a type, and must have an explicit type. [MESH_ERROR_STRING] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\comprobaciones.f90 206
Error error #6362: The data types of the argument(s) are invalid. [TRIM] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\comprobaciones.f90 206
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\conlud.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\derff.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\ef_el.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\electrostatica3D.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\endat3D.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\ensacmor.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\funciones3D.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\gauspp.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leema3D.f90 1
Error Compilation Aborted (code 1) C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leema3D.f90 1
Error error #7002: Error in opening the compiled module file. Check INCLUDE paths. [MODULE_COMPILER_DEPENDANT] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leema3D.f90 19
Error error #6580: Name in only-list does not exist. [IOSTAT_END] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leema3D.f90 19
Error error #7002: Error in opening the compiled module file. Check INCLUDE paths. [MODULE_CONVER3D] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leema3D.f90 24
Error error #6580: Name in only-list does not exist. [CONVER3D] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leema3D.f90 24
Error error #6404: This name does not have a type, and must have an explicit type. [IOSTAT_END] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leema3D.f90 89
Error error #6406: Conflicting attributes or multiple declaration of name. [CONVER3D] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leema3D.f90 90
Error error #6406: Conflicting attributes or multiple declaration of name. [CONVER3D] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leema3D.f90 170
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leetmp.f90 1
Error Compilation Aborted (code 1) C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leetmp.f90 1
Error error #7002: Error in opening the compiled module file. Check INCLUDE paths. [MODULE_CONVERS] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leetmp.f90 9
Error error #7002: Error in opening the compiled module file. Check INCLUDE paths. [LIB_VTK_IO_READ] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leetmp.f90 10
Error error #6404: This name does not have a type, and must have an explicit type. [LCASE] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leetmp.f90 19
Error error #6608: In a CASE statement, the case-expr must be of type INTEGER, CHARACTER, or LOGICAL. [LCASE] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leetmp.f90 19
Error error #6611: The case-value must be of the same type as the case-expr. ['mff'] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leetmp.f90 20
Error error #6611: The case-value must be of the same type as the case-expr. ['vtu'] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leetmp.f90 31
Error error #6404: This name does not have a type, and must have an explicit type. [VTK_INI_XML_READ] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leetmp.f90 33
Error error #6404: This name does not have a type, and must have an explicit type. [VTK_VAR_XML_READ] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leetmp.f90 36
Error error #6404: This name does not have a type, and must have an explicit type. [VTK_END_XML_READ] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\leetmp.f90 38
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\matlap_orto.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\matriz3D_orto.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\matvec.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\modulos_electros3D.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\mod_mcambio.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\norl2_3D.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 1
Error Compilation Aborted (code 1) C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 1
Error error #7002: Error in opening the compiled module file. Check INCLUDE paths. [MODULE_WRITEVTU] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 29
Error error #7002: Error in opening the compiled module file. Check INCLUDE paths. [COMPROBACIONES] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 30
Error error #7002: Error in opening the compiled module file. Check INCLUDE paths. [MODULE_CONVERS] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 31
Error error #7002: Error in opening the compiled module file. Check INCLUDE paths. [MODULE_FEM_EXTRACT] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 32
Error error #7002: Error in opening the compiled module file. Check INCLUDE paths. [MODULE_CONVER3D] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 33
Error error #6580: Name in only-list does not exist. [CONVER3D] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 33
Error error #7002: Error in opening the compiled module file. Check INCLUDE paths. [LIB_VTK_IO_READ] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 34
Error error #7002: Error in opening the compiled module file. Check INCLUDE paths. [MODULE_READUNV] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 35
Error error #7002: Error in opening the compiled module file. Check INCLUDE paths. [MODULE_COMPILER_DEPENDANT] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 36
Error error #6683: A kind type parameter must be a compile-time constant. [REAL64] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 41
Error error #6404: This name does not have a type, and must have an explicit type. [COMPRUEBA] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 54
Error error #6404: This name does not have a type, and must have an explicit type. [ERROR_UNIT] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 55
Error error #6404: This name does not have a type, and must have an explicit type. [OUTPUT_UNIT] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 58
Error error #6404: This name does not have a type, and must have an explicit type. [BLOCKING_NODE] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 64
Error error #6404: This name does not have a type, and must have an explicit type. [LCASE] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 76
Error error #6608: In a CASE statement, the case-expr must be of type INTEGER, CHARACTER, or LOGICAL. [LCASE] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 76
Error error #6611: The case-value must be of the same type as the case-expr. ['mfm'] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 77
Error error #6611: The case-value must be of the same type as the case-expr. ['mum'] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 80
Error error #6611: The case-value must be of the same type as the case-expr. ['unv'] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 83
Error error #6406: Conflicting attributes or multiple declaration of name. [CONVER3D] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\principal.f90 85
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\procb1.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\procb2.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\psolve.f90 1
Error error code 23 (returned by OpenValidateX) opening pdb Debug\vc140.pdb C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\punto1.f90 1
Error Compilation Aborted (code 1) C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\readxml.f90 1
Error error #7002: Error in opening the compiled module file. Check INCLUDE paths. [MODULE_SO_DEPENDANT] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\readxml.f90 7
Error error #7002: Error in opening the compiled module file. Check INCLUDE paths. [MODULE_REPORT] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\readxml.f90 8
Error error #7002: Error in opening the compiled module file. Check INCLUDE paths. [MODULE_XML_PARSER] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\readxml.f90 9
Error error #6683: A kind type parameter must be a compile-time constant. [DOUBLE] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\readxml.f90 24
Error error #6683: A kind type parameter must be a compile-time constant. [DOUBLE] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\readxml.f90 25
Error error #6404: This name does not have a type, and must have an explicit type. [REPORT_STDOUT] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\readxml.f90 29
Error error #6404: This name does not have a type, and must have an explicit type. [FOPEN] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\readxml.f90 39
Error error #6632: Keyword arguments are invalid without an explicit interface. [REALLOC] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\readxml.f90 58
Error error #6362: The data types of the argument(s) are invalid. [INT] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\readxml.f90 66
Error error #6632: Keyword arguments are invalid without an explicit interface. [REALLOC] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\readxml.f90 77
Error error #6362: The data types of the argument(s) are invalid. [INT] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\readxml.f90 85
Error error #6632: Keyword arguments are invalid without an explicit interface. [REALLOC] C:\Users\admin\Documents\maxfem test for ifort A\maxfem_0.3.4_source\maxfem_0.3.4_source\sources\electrostatics3d\readxml.f90 110
...
what should I do, any help will be appreciated.

updated #1 my Makefile.windows is as below:

#################################################################
# Makefile created using the tool 'Creamake'
#
# Creamake is distributed under the GNU GPL license
# Author: Francisco Pena, fran.pena@usc.es
# Download page: http://sourceforge.net/projects/creamake/
#################################################################

#################################################################
# User-modifiable options
#################################################################

# SOURCE AND COMMONS FOLDERS (separated by spaces)
dir_fuentes = . ..\other\blas ..\other\basicmod ..\other\common ..\other\fem \
..\other\unv ..\other\xml ..\other\vtu ..\other\conver3d

# OBJECT AND .MOD FOLDER
dir_objetos = object

# MAIN SOURCE FILE (include relative path from folder where Makefile is)
condir_principal = .\principal.f90

# EXECUTABLE NAME
ejecutable = ..\..\solvers\electrostatics3d.exe

# NEEDED TO convert ejecutable THE DEFAULT RULE:
$(ejecutable): $(condir_principal)

# MODULES
modulos = comprobaciones.f90 mod_mcambio.f90 modulos_electros3D.f90 \
module_ALLOC_char_r1.f90 module_ALLOC.f90 module_ALLOC_int_alloc_r2.f90 \
module_ALLOC_int_r1.f90 module_ALLOC_int_r2.f90 module_ALLOC_log_r2.f90 \
module_ALLOC_real_alloc_r2.f90 module_ALLOC_real_DOUBLE_r1.f90 \
module_ALLOC_real_DOUBLE_r2.f90 module_ALLOC_real_r1.f90 \
module_ALLOC_real_r2.f90 module_COMPILER_DEPENDANT.f90 module_CONVERS.f90 \
module_FILES.f90 module_REPORT.f90 module_SO_DEPENDANT.f90 defines.f90 mesh.f90 \
subdomains.f90 vector.f90 module_fem_extract_complex.f90 module_fem_extract.f90 \
module_fem_extract_real.f90 module_bsearch.f90 module_cells.f90 \
module_dataset_2411.f90 module_dataset_2412.f90 module_dataset_2467.f90 \
module_dataset.f90 module_FE_DB.f90 module_groups.f90 module_mesh.f90 \
module_readUNV.f90 module_unv.f90 module_xml_parser.f90 LIB_VTK_IO.f90 \
LIB_VTK_IO_READ.f90 module_writeVTU.f90 module_conver3d.f90 \
module_conver3d_source.f

# DEPENDENCIAS ENTRE MODULOS
# si pru1 depende de pru2... pru1.o: pru2.o
comprobaciones.obj: mesh.obj modulos_electros3D.obj modulos_electros3D.obj \
modulos_electros3D.obj modulos_electros3D.obj modulos_electros3D.obj \
modulos_electros3D.obj modulos_electros3D.obj modulos_electros3D.obj \
modulos_electros3D.obj
mod_mcambio.obj: modulos_electros3D.obj
modulos_electros3D.obj:
module_ALLOC_char_r1.obj: module_REPORT.obj
module_ALLOC.obj: module_ALLOC_int_r1.obj module_ALLOC_int_r2.obj \
module_ALLOC_int_alloc_r2.obj module_ALLOC_real_r1.obj module_ALLOC_real_r2.obj \
module_ALLOC_real_alloc_r2.obj module_ALLOC_real_DOUBLE_r1.obj \
module_ALLOC_real_DOUBLE_r2.obj module_ALLOC_char_r1.obj module_ALLOC_log_r2.obj
module_ALLOC_int_alloc_r2.obj: module_ALLOC_int_r1.obj
module_ALLOC_int_r1.obj: module_REPORT.obj
module_ALLOC_int_r2.obj: module_REPORT.obj
module_ALLOC_log_r2.obj: module_REPORT.obj
module_ALLOC_real_alloc_r2.obj: module_ALLOC_real_r1.obj
module_ALLOC_real_DOUBLE_r1.obj: module_COMPILER_DEPENDANT.obj module_REPORT.obj
module_ALLOC_real_DOUBLE_r2.obj: module_COMPILER_DEPENDANT.obj module_REPORT.obj
module_ALLOC_real_r1.obj: module_REPORT.obj
module_ALLOC_real_r2.obj: module_REPORT.obj
module_CONVERS.obj: module_COMPILER_DEPENDANT.obj module_REPORT.obj
module_FILES.obj: module_REPORT.obj module_CONVERS.obj
module_REPORT.obj: module_COMPILER_DEPENDANT.obj module_SO_DEPENDANT.obj
module_SO_DEPENDANT.obj: module_COMPILER_DEPENDANT.obj
defines.obj: module_COMPILER_DEPENDANT.obj
mesh.obj: defines.obj
subdomains.obj: defines.obj
vector.obj: defines.obj
module_fem_extract.obj: module_fem_extract_real.obj \
module_fem_extract_complex.obj
module_dataset_2411.obj: module_COMPILER_DEPENDANT.obj module_ALLOC.obj \
module_dataset.obj module_mesh.obj
module_dataset_2412.obj: module_ALLOC.obj module_dataset.obj module_mesh.obj \
module_FE_DB.obj module_cells.obj
module_dataset_2467.obj: module_dataset.obj module_mesh.obj module_cells.obj \
module_groups.obj
module_dataset.obj: module_REPORT.obj module_CONVERS.obj
module_FE_DB.obj: module_COMPILER_DEPENDANT.obj
module_groups.obj: module_ALLOC.obj
module_mesh.obj: module_COMPILER_DEPENDANT.obj module_ALLOC.obj module_FILES.obj
module_readUNV.obj: module_COMPILER_DEPENDANT.obj module_SO_DEPENDANT.obj \
module_CONVERS.obj module_unv.obj module_mesh.obj
module_unv.obj: module_ALLOC.obj module_FILES.obj module_mesh.obj \
module_dataset_2411.obj module_dataset_2412.obj module_dataset_2467.obj \
module_bsearch.obj
module_xml_parser.obj: module_ALLOC.obj module_CONVERS.obj module_REPORT.obj \
module_FILES.obj
LIB_VTK_IO_READ.obj: LIB_VTK_IO.obj
module_writeVTU.obj: LIB_VTK_IO.obj
module_conver3d.obj: module_COMPILER_DEPENDANT.obj module_conver3d_source.obj

# INCLUDES
includes =

# COMPILER
FC = gfortran

# COMPILER OPTIONS
FFLAGS = -J$(dir_objetos) -ffree-line-length-0 -ffixed-line-length-0

# LINKER OPTIONS
LDFLAGS = -static

#################################################################
# Non-modifiable part
#################################################################

# CARPETAS DE BUSQUEDA
VPATH = $(subst ,:,$(strip $(dir_fuentes)))
vpath %.obj $(dir_objetos)

# FUENTES
fuentes_ = $(filter %.f %.F %.for %.FOR %.f90 %.F90 %.f95 %.F95 %.f03 %.F03,$(shell dir /b $(dir_fuentes)))
fuentes = $(filter-out $(notdir $(condir_principal)) $(modulos),$(fuentes_))

# OBJETOS
modulos_obj = $(addsuffix .obj,$(basename $(modulos)))
fuentes_obj = $(addsuffix .obj,$(basename $(fuentes)))

# OBJETOS EN SU CARPETA
condir_modulos_obj = $(addprefix $(dir_objetos)/,$(modulos_obj))
condir_fuentes_obj = $(addprefix $(dir_objetos)/,$(fuentes_obj))

# OPCIONES DE COMPILACION
FFLAGS += $(patsubst %,-I%,$(dir_fuentes))
FFLAGS += -I$(dir_objetos)

# REGLA PRINCIPAL
all: $(ejecutable)

$(ejecutable): $(includes) $(modulos_obj) $(fuentes_obj)
$(FC) -o $(ejecutable) $(FFLAGS) $(condir_principal) $(condir_modulos_obj) $(condir_fuentes_obj) $(LDFLAGS)

# REGLA PARA LAS FUENTES
$(fuentes_obj): $(includes) $(modulos_obj)

# PATRONES DE REGLAS
%.obj:%.f
$(FC) -c -o $@ $(FFLAGS) $<
@copy $@ $(dir_objetos)
@del $@
%.obj:%.F
$(FC) -c -o $@ $(FFLAGS) $<
@copy $@ $(dir_objetos)
@del $@
%.obj:%.for
$(FC) -c -o $@ $(FFLAGS) $<
@copy $@ $(dir_objetos)
@del $@
%.obj:%.FOR
$(FC) -c -o $@ $(FFLAGS) $<
@copy $@ $(dir_objetos)
@del $@
%.obj:%.f90
$(FC) -c -o $@ $(FFLAGS) $<
@copy $@ $(dir_objetos)
@del $@
%.obj:%.F90
$(FC) -c -o $@ $(FFLAGS) $<
@copy $@ $(dir_objetos)
@del $@

.PHONY: clean
clean:
del $(dir_objetos)\*.obj
del $(dir_objetos)\*.mod
del $(ejecutable)

Hey. I am working on a Fortran 77 code in Visual Studio 2015, and when I type in a Blank behind the 72th column (stack overflow) a white field appears, as illustrated in the image below.

How can I disable this function?

Thanks for your help. 

Hi,

I am using VS2013 update 4.

I noticed this problem as I installed Parallel Studio 2017 update 2 and it persist for update 4.

Compiler output in VS output window prints warnings and errors in source files as usual. But the file paths it provides are messed up with forward slash before the file names.

For example:

My file is located at

d:\tmp\a.f

If there is an error or a warning in the file, VS prints:

D:\tmp/a.f(1850): warning #6717: This name has not been given an explicit type.   [IERR]

When I double click on the message to correct the issue, VS opens another tab for the file even though the file has already been opened in VS with d:\tmp\a.f path. Then, VS complains that the file has been edited outside of the source editor. This is SO frustrating...

Hi all,

I'm getting a strange array out of bounds error when I try to print a 2D array by row in a contained procedure. I'm using the latest version of IVF with VS Community 2015 and all the default settings. 

I have a hacky fix which is included in the snippet below, but just wondered if anyone could help; am I at fault, or is this a bug? I think its something to do with allocating a temporary array for a write statement, but perhaps someone who knows a bit more could explain?

Thanks,

Michael 

 program LowerBoundError

    implicit none

    integer, parameter :: dim = 3
    double precision :: bigVector( dim * dim )
    integer :: iGlb

    ! Initialize
    bigVector = 0

    call WriteArrays( dim, bigVector )

    contains

    subroutine WriteArrays( d, b )
        integer, intent(in) :: d
        double precision, intent(in) :: b(:)
        double precision :: tmp(d)
        integer :: i

        write(*,*) d
        write(*,*) b

        ! write by row
        do i = 1, d
            ! This crashes
            write(*,*) b( i : : d )

            ! However this works
            tmp = b( i : : d )
            write(*,*) tmp
        end do
    end subroutine WriteArrays

end program LowerBoundError

and the error message:

an error forrtl: severe (408): fort: (3): Subscript #1 of the array B has value -858993460 which is less than the lower bound of 1