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

Further IFX annoyances

JohnNichols
Valued Contributor III
4,360 Views

Screenshot 2024-01-17 110853.png

 

 

This works, 

Screenshot 2024-01-17 111003.png

This does not for R,  allocated

Screenshot 2024-01-18 111643.png

More of the same

Screenshot 2024-01-20 081531.png

numR is 16384, which is a mistake as it is supposed to be a power of 2 and that is not, but it is definitely defined.  

Screenshot 2024-01-20 082141.png

dum is an integer and is defined and I can see it in the code.  

Any idea when we can expect a fix.  DISLIN works with IFX but not really well with IFORT, so I do not want to go back.  

I am using the old FORTRAN expedient of write(*,*) dum

 

 

 

 

 

0 Kudos
22 Replies
JohnNichols
Valued Contributor III
386 Views

I have reinstalled everything and am only using VS 2022.  

Screenshot 2024-01-25 133508.png

I worked out what is causing the most annoying issue, the parameter FFT_small is defined in a module - Base - as a integer parameter. 

N is an integer passed to the routine as an argument and has the same integer value as FFT_small.  

I changed Y3RAY to be defined with FFT_small instead of N.  You can see the difference in the debugger, I assume this is the Fortran debugger.  The output depends on whether you use a parameter or a variable.  

0 Kudos
Steve_Lionel
Honored Contributor III
354 Views

Now you have the Fortran debug support working.

PARAMETER constants from modules aren't brought in by default. You can use the syntax modname::name in a watch window. Also see the option /debug:parameters.

0 Kudos
Reply