parser problem?

parser problem?


I use ifort version 12.1.5
I encountered a problem when compiling this little piece of code:

      program testtype

      implicit none
      integer :: type16_ix, type20_iy
      integer :: type_16_ix, type_20_iy
      integer :: typex6_ix, typey0_iy

      type16_ix = 5
      type20_iy = 100

      type_16_ix = 5
      type_20_iy = 100

      typex6_ix = 5
      typey0_iy = 100

      write (*,*) type16_ix, type20_iy
      write (*,*) type_16_ix, type_20_iy
      write (*,*) typex6_ix, typey0_iy


The result given by the compiler is:

ifort -o testtype testtype.f                                                                          
testtype.f(8): error #6404: This name does not have a type, and must have an explicit type.   [TYPE6_IX]                
      type16_ix = 5                                                                                                     
testtype.f(9): error #6404: This name does not have a type, and must have an explicit type.   [TYPE0_IY]                
      type20_iy = 100                                                                                                   
compilation aborted for testtype.f (code 1)

To me it looks like a parser problem. 

Well, I know how to circumvent it. But the problem should be brought to the attention of the compiler developer.

Have fun


(See for replies - forum bug. - Steve L)

publicaciones de 4 / 0 nuevos
Último envío
Para obtener más información sobre las optimizaciones del compilador, consulte el aviso sobre la optimización.

I don't encounter the problem with the compiler 13.0.1.

This is a problem only when fixed-form source is used. It is very strange! I have escalated this as issue DPD200239834 - thanks for bringing it to our attention.

Steve - Intel Developer Support

I expect this problem to be fixed in Update 3 (end of March).

Steve - Intel Developer Support

Deje un comentario

Por favor inicie sesión para agregar un comentario. ¿No es socio? Únase ya