Last = GetSADFloatRel(input, &fSamples.at(offset), w * 4 + 1, w * 4 + 1, 0) Otherwise just make it private.Īccess to bestHit, cVal, rad, and veneOffset should be synchronised by a critical region: #pragma omp critical Last is only assigned to before it is read again so it is a good candidate for being a lastprivate variable, if you really need the value from the last iteration outside the parallel region. Last = GetSADFloatRel(adapted, &fSamples.at(offset), 4*w+1, 4*w+1, 0) To elaborate on my comment, this is the code that is most probably the root of your problem: #pragma omp parallel for shared(last, bestHit, cVal, rad, veneOffset) Debug mode and OpenMP activated gets a different result, OpenMP deactivated gets the same result as with Release. Note: with Release mode and OpenMP activated I get the same result as with deactivating OpenMP. Update1: The code I now found responsible for this behaviour: float PatternMatcher::GetSADFloatRel(float* sample, float* compared, int sampleX, int compX, int offX) I've already checked whether it may be thread related, but the only part in the algorithm which is multi-threaded returns the precisely same result for both debug and release. The main issue I have with this is that the complete image analysis (its an image understanding project) is completely deterministic, there's absolutely nothing random in it.Īnother issue with this is the fact that my release build actually always returns the same result (23.014 for the image), while debug returns some random value between 22 and 23, which just should not be. I checked that both modes use /fp:precise, so that should not be the problem.

I have the problem that my code returns different results when comparing debug to release.

Aw2 emulator mac