CVF: differences in results depending on "debugging level"

[forall]

I am trying to track down the cause of fairly different computational results in debug and release configurations (using CVF) and eventually found that the differences occur depending on the "debugging level" setting: "full debugging" vs "minimal"/"partial" (ironically, the full debug results seem consistently better and more in line with some theoretical expecations about the algorithm).

Does this make sense? From reading the documentation it seems that this option (debugging level) should not change the executable structure of the code, just add information allowing to see the variables in the debugger.

thanks in advance.

Message Edited by forall on 08-30-2005 01:11 PM

[Steven_L_Intel1]

Yes, I have seen this. The compiler needs to generate some different code for arrays when debugging is requested, and this can change the behavior. There have also been bugs which would occur when debugging was not specified (or was specified).