Generate interface blocks

[Les_Neilson]

Using ivf 9.1 with Visual Studio .Net 2003

I have a directory with 170 source files used to build a lib. some of the source files contain more than one subroutine. One in particular has 32 subroutines. Normally compilation is ok; but recently I selected the option Project properties->Fortran diagnostics->Check routine interfaces along with Fortran External Procedures->Generate Interface Blocks and this one file causes thecompiler to "hang" after all of the *_mod.f90 and *_mod.mod fileshave been created. The name of the file is printed in the output window but it never completes. The .obj file is zero bytes.

I must add that testing the settings individuallyit is the Generate Interface Blocks options that causes the compiler to hang.

Looking atprocess explorer the ifort.exe (fortcom.exe)is still listed, but taking no cpu time.

I am able to reproduce this with a small project with just this one file. But before I submitted an Issue I wondered if anyone herehad a similar experience and possible answer.

Thanks

Les

[jugoslavdujic2]

Experience – yes :-(

Answer – no :-((

[Les_Neilson]

LOL :-)

Les

[dbruceg]

Les:

Steve made that look easy in an earlier thread. I've been using it for about a week now, and if you can just get it going, it works pretty good. As for getting it going, there appear to be several problems in there, one of which is one you've mentioned. I have no idea why, but I have been able to stumble through the compilation of a few intransigent files by deleting the associated .mod files if they exist (I route them to their own directory) and recompiling the individual files. Once, I got away with deleting ALL the .mod files and rebuilding the entire package (rebuild does not appear to clean up existing .mod files). I'd like to offer more than a recount of my blind luck, but...

Bruce

[Steven_L_Intel1]

The "answer" is that you've found a bug and you should report it, along with the errant source, so that we can fix it. Before you do so, make sure you're using the latest compiler (which is 9.1.025 as of this writing.)

[AONym]

I had previously found this bug and reported it to Premier Support, who have verified it as a bug. No indication from them when it will be fixed.

Only a few source files in a 200+ file project have this problem, and it only occurs when the files are compiled in a certain order.