Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.

Problem with new Fortran

garraleta_fortran
5 330 Visites
The version of FORTRAN and Visual Studio is:

Intel® FORTRAN Compiler 2025.0.4 [Intel(R) 64]
Microsoft Visual Studio Community 2022 (64-bit) - Current Version 17.13.3

There is no problem with the old version of FORTRAN.

The version of FORTRAN and Visual Studio is:

Intel(R) Visual FORTRAN Package ID: w_fcompxe_2013.2.149
Microsoft Visual Studio Team System 2008 Architecture Edition 1899-270-2717477-60709


I attach two ZIP files with the projects of both solutions
0 Compliments
10 Réponses
Devorah_H_Intel
Modérateur
5 275 Visites

with upcoming 2025.1 ifx:

 

Screenshot 2025-03-17 153708.png

0 Compliments
garraleta_fortran
4 632 Visites

Debug problems with new FORTRAN

0 Compliments
JohnNichols
Contributeur émérite I
4 552 Visites
module datos
    TYPE Vector
    integer(4) :: X
    integer(4) :: Y
    end type vector
    end module datos
    
    
    program mainer
    
    USE DATOS
USE ISO_FORTRAN_ENV
IMPLICIT NONE
TYPE(VECTOR) :: V
OPEN(UNIT=1,FILE='RES.TXT')

WRITE(1,FMT='(A)')COMPILER_VERSION()

V.X=100
V.Y=200
WRITE(1,*)'VP',V.X,V.Y
CALL SUB1(V)
CALL SUB2(V)
CALL SUB3(V)
CLOSE(UNIT=1)
END

SUBROUTINE SUB1(V1)
USE DATOS
IMPLICIT NONE
TYPE(VECTOR) :: V1
WRITE(1,*)'V1',&
V1.X,V1.Y
RETURN 
END    


SUBROUTINE SUB3(V3)
USE DATOS
IMPLICIT NONE
TYPE(VECTOR) :: V3
WRITE(1,*)'V3',&
V3.X,V3.Y 
RETURN
END    


SUBROUTINE SUB2(V2)
USE DATOS
IMPLICIT NONE
TYPE(VECTOR) :: V2
WRITE(1,*)'V2',&
V2.X,V2.Y
RETURN  
END    

 

Your Fortran is spread across five modules, you left one out, I found it in the bmp. 

Here it is as one program. 

It is running on a COREi7, latest Windows Preview, latest VS 2022 Preview and the latest update to the 2025.2.1 release.  You cannot be more up to date than this. 

The shots of the debug screen as I step through your program in one file.  Notice that you only see the debug for the current subroutine.

 

Screenshot 2025-09-13 113726.png

 

Screenshot 2025-09-13 113724.png

Screenshot 2025-09-13 113833.png

 

Screenshot 2025-09-13 113920.png

 

Screenshot 2025-09-13 113927.png

 

Screenshot 2025-09-13 113959.png

Just as expected. 

Your picture shows the open files and the files that do not have focus show 

 

P1.png

 

XX shows the notification that the subroutine does not have focus so it is not updated as you step through V3.F90 , NN is normal as you have focus on V3.F90 according to the break point cursor.  I can see all of your values as required, this is absolutely all you need. 

Once you have left V1 then any good garbage collector in other languages could clean it up. 

0 Compliments
garraleta_fortran
4 234 Visites

If the main program, mudule and subroutines are in the same file, it works fine.
Attached video

0 Compliments
JohnNichols
Contributeur émérite I
4 228 Visites

I understand what you are saying and I watched the video, but exactly what do you want the program to do in debugging. 

You need to provide an explanation. 

0 Compliments
garraleta_fortran
4 216 Visites

I should do this.
Like Intel(R) Visual Fortran Compiler XE 13.1

0 Compliments
garraleta_fortran
3 396 Visites

With th new version 2025.3.0.324 work !!!! OK ¡¡¡¡

0 Compliments
garraleta_fortran
5 107 Visites

"WHEN WILL VERSION 2025.1 ifx BE AVAILABLE?

0 Compliments
Devorah_H_Intel
Modérateur
5 072 Visites

@garraleta_fortran wrote:

"WHEN WILL VERSION 2025.1 ifx BE AVAILABLE?


2025.1 is coming out within a week. 

0 Compliments
JohnNichols
Contributeur émérite I
4 187 Visites

Screenshot 2025-09-14 114124.png

Please do not use bitmaps, bmp will not upload and I need to change them to png. 

0 Compliments
Répondre