Compiler directive scope changes

[fohfab]

Has there been a change in the 'scope' of the compiler souce format directive NOFREEFORM in Intel 12.1?

The reason I ask is that I have a .f90 file with NOFREEFORM dirctive, which includes a .inc file (which also has the NOFREEFORM directive. But source after this include is being compiled as if it were free fomat (and so producing errors). The project format is set to be 'use source extension'.

It looks like when returning to the .f90 file, the format is returning to the project setting rather than the compiler directive at the top of the source file.

Can you confirm this and is it a bug?

[Steven_L_Intel1]

I can't reproduce this. Please attach a test case.

[fohfab]

I can't reproduce it in a test case either! I need to work on it and send you something that shows the error.

[fohfab]

That was interesting. It looks like 'the bug' is connected to the /warn:interfaces switch. If you unzip the attached files and type ifort /c /fpp /warn:interfaces mf_load.f90 you will see a compiler error that implies that the format type has reverted to free format after the include files. If you add !DEC$ NOFREEFORM after the include then the compiler is happy!

[Steven_L_Intel1]

Interesting. We fixed a bug very much like this in 12.0 and the test case for that one still works, but yours does not. I will report this to the developers.

[fohfab]

Thanks Steve. I will leave it with you. We have a workround in either switching off the /warn:interfaces or adding the NOFREEFORM compiler directive after the include, so we can continue with version 12.1.
Thanks.

[Steven_L_Intel1]

Escalated as DPD200174491.

[Steven_L_Intel1]

Fixed for a future release.