Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Avisos
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.

.f95 files in VS IDE

scrognoid
Principiante
1.515 Vistas

I am evaluating the latest Intel Fortran Compiler in the VS 2005 IDE. I can't compile my project consisting of several dozen *.f95 files.

I tried Tools>Options>Fortran>General and added .f95 and restarted VS. No effect:

Warning 1 command line warning #10161: unrecognized source type 'E:\TimDocs\fort\fft_auto\source\q2imask_module.f95'; object file assumed ifort

Based on a thread here, I tried Project>Properties>Fortran>Command Line and added /extfor:.f95. ifort now tries to compile, but apparently doesn't recognize the file content:

module q2imask_module
contains

subroutine q2imask(qmask,imask,li)

...

Generated errors on every character:

Error 1 error #5149: Illegal character in statement label field E:\TimDocs\fort\fft_auto\source\q2imask_module.f95 1
Error 2 error #5149: Illegal character in statement label field E:\TimDocs\fort\fft_auto\source\q2imask_module.f95 1
Error 3 error #5149: Illegal character in statement label field E:\TimDocs\fort\fft_auto\source\q2imask_module.f95 1

Any help?

0 kudos
1 Solución
Steven_L_Intel1
Empleados
1.515 Vistas

This is a known problem and should be fixed in a future update. All I can suggest is what I would normally recommend - do not use .f95, .f03 or other non-industry-standard file type. It is a common misconception that the file type designates the standards revision level. All it does is distinguish free-form from fixed-form source. Please use the .f90 file type for your free-form source. Our issue ID is DPD200049917.

A possible workaround is to add the command line option /free to Additional Options under Command Line.

Ver la solución en mensaje original publicado

1 Responder
Steven_L_Intel1
Empleados
1.516 Vistas

This is a known problem and should be fixed in a future update. All I can suggest is what I would normally recommend - do not use .f95, .f03 or other non-industry-standard file type. It is a common misconception that the file type designates the standards revision level. All it does is distinguish free-form from fixed-form source. Please use the .f90 file type for your free-form source. Our issue ID is DPD200049917.

A possible workaround is to add the command line option /free to Additional Options under Command Line.

Responder