v16 compiler breaks code

[rorban]

I have a complicated real-time dll signal processor project that has been compiling without problems with Composer Professional Edition v15.3. This project is part of a commercial product that is current available for sale. Today I tried the new release of v16 and it seriously broke the project. It built OK (no error messages) and the dll doesn't crash. (I know this because it passed metering information about the input to the host application, an MS C++ project). However, the v16 build did not pass signal to the processing or output, even when run in a simplified "bypass" mode that basically connects the input to the output.

The code uses IMPLICIT NONE and modules for everything, to give the subroutines and functions explicit interfaces. It uses the standard F2003 C interoperability features. For the sake of execution speed (enormously important in this application), I did not use any of the fancy new F2003 OO features like type-bound procedures, assuming that the compiler's support for conventional subroutines and functions would be more mature and optimization would likely be better. Bottom line: the project is written in a conservative, standards-based style that attempts to maximize both the ability of the code be to be optimized and the compiler's ability to detect errors. There is no code in it that could trigger some of the bugs in cutting-edge features that have been reported on this forum.

I tried turning off optimization, but this did not help.

I did a System Restore in Windows to restore the v15.3 compiler, rebuilt the project, and the dll works again.

It later occurred to me that maybe the redistributable libraries did not update properly on my build machine, but V16 does not yet show up in the Intel "Redistributable library" page.

I know that this is all very vague, but I really haven't a clue as to how to troubleshoot the problem (other than to check the libraries). Unfortunately, the realtime nature of the project requires optimization for speed for it to work without creating gaps in the signal (due to newer input being received before the previous input could be processed). So I don't think that the debugger can be used. (After doing some testing in an earlier version of my code with runtime features turned on to detect possible out-of-bounds arrays, I have since been debugging with traditional bench tools like oscilloscopes and spectrum analyzers.)

So I'm not expecting an answer, but wanted to report the problem. For the moment, I will stick with v15.3 and get on with it.

[Kevin_D_Intel]

Thank you for your post. We're sorry to hear about the problems with our 16.0 release. I hope the issue can be resolved in the future so you are able to take advantage of newer releases.

I realize you are sticking with v15.3 for now so this information may not be of interest immediately; however, I did want to note the Redistributable Library package is available from the Intel® Software Development Products Registration Center (IRC). This appears under the specific downloads for the Intel® Parallel Studio XE Composer Edition for Fortran Windows* product in the Related Files section. The current version is named ww_ifort_redist_msi_2016.0.110.zip. We will also be updating the Redistributable page that you noted soon.