Debug vs. Release mode result

[elquin]

Dear all,

I'm constructing huge code with IVF and IMSL, the original was CVF but the migration from CVF to IVF was done in confidence.

When compiling in debug mode with IMSL, some test cases show different result with debug and release mode.

Also, some test runs need to IMSL license check when run with debug exe file.

I wonder how can I solve this problems.

regards,

h.kim

[mecej4]

Have you read the information given in the link Migrating from CVF ? In particular, have to made the adjustments to accommodate (i) by default local variables are SAVEd in CVF, AUTOMATIC in IVF, and (ii) calling conventions are different.

Which versions of CVF and IVF did you use? Which version(s) of IMSL?

I'm afraid that in a project such as this is is much more difficult to make the program work correctly than to get it to compile and link without errors.

[bmchenry]

I'd recommend recompiling both debug and release withthe option:
/Qimf-arch-consistency:true
which
"ensures that the math library functions produce consistent results across different implementations of the same architecture"
It makes somewhat slower code (but what is 'slow' these days?)
Andthen you should find results the same orcloser to the old CSV results.
One other item is that the difference between yourdebug v release code may be optimization.
So turn off optimization in the early going to get code consistent.
Thenyou can try different optimization levels.

[elquin]

My present environments are ;

MS Visual Studio 2008
Intel Visual Fortran v11.1.065
IMSL Library 6.0 for Intel Fortran Compiler 11.0 - IA-32

But not sure about the version of CVF because I failed to install CVF in my PC.
I already read docs you mentioned above and sure that the migration from CVF to IVF is done correctly.

Thank you,

[SergeyKostrov]

Quoting elquin

...some test cases show different result with debug and release mode...

Hi,

Could you give at least one example? What abouta simple Test-Case?

Best regards,
Sergey

[John_B__Walter]

If you have the "project".dsw file from the CVF project, the first line is something like

[bash]Microsoft Developer Studio Workspace File, Format Version 6.00[/bash]

The format version, 6.00 in this example, should be the CVF version that was used, as I understand it. The example I took this from was last used with CVF 6.00. Since then I've switched to IVF which doesn't use this .dsw file, except to create the solution and project files that it uses. This leaves the .dsw file hanging around, so you can open it in a text editor.