Continuation lines issue with ifort

[kserradell]

Hello

I'm porting a code to ifort which is compiling correctly with IBM xlf compiler.

When I compile with ifort I've got problems with this continuation lines:

INTEGER kpdtsf,kpdwet,kpdsno,kpdzor,kpdais,kpdtg3,kpdplr,kpdgla,
& kpdmxi,kpdscv,kpdsmc,kpdoro,kpdmsk,kpdstc,kpdacn,kpdveg,
& kpdvet,kpdsot

& is in the beggining of the line, and ifort throws a syntax error.

The workaround is to manually insert & at the end of the line, like this

INTEGER kpdtsf,kpdwet,kpdsno,kpdzor,kpdais,kpdtg3,kpdplr,kpdgla, &
& kpdmxi,kpdscv,kpdsmc,kpdoro,kpdmsk,kpdstc,kpdacn,kpdveg, &
& kpdvet,kpdsot

But there are thousands of code lines (also doing with sed is quite difficult beacuse there are comments and other stuff...).

Is there any compilation flag to compile this syntax ? Or another workaround ?

Thank you very much,

Kim

[Kevin_D_Intel · Accepted solution]

Is your source Fixed or Free format?

I can't tell from the code snippet in your post if some additional indentation was lost but the line continuation shown hints the source may be Fixed format and if so and those lines cause compile errors then that, and your work around, suggests the source was compiled as Free format by ifort. Unless overridden by a compiler option or directive, the source file suffix determines the source form applied at compilation.

If you use a Free form file suffix (.f90, .F90) but the source is Fixed form, thenyou can set the source format to Fixed with the compiler option: -fixed

Or use a file suffix that implies Fixed form, e.g. .f, .for, .FOR, .ftn, .FTN

[kserradell]

Thank you Kevin !!!

It was this !!! I building a code that is quite a mess and there free and fixed forms mixed.

Thank you again !!!

KiM

[mecej4]

In the few original lines that were shown, the character '&' is preceded by five blanks, suggesting that the source is in fixed format. If this description applies to the entire code, all that you have to do is to follow the suggestions of Kevin Davis. My preference would be to use the file suffix '.f'.

[Kevin_D_Intel]

You're welcome, Kim. Glad that helped.