Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
29235 Discussions

Problems building "Release" version in a double quad-core

gattorognoso
Beginner
565 Views
I am trying to build a "release" version of a code, with a double processor -quad core (8 cores in total) Intel Xeon CPU X5355 @ 2.66GHz, 16.GB of RAM.
The OS is Windows XP Professional x64 Edition version 2003.
I am using VS 2005 and Fortran w_fc_p_10.1.021_ia32.exe and the recent x64 version.
The code stops for some routine problems, but the same version is perfectly working with a "debug" version on the same machine, and in "debug" and "release" mode on different machines (one of them is a intel xeon CPU 2.80GHz, 1.00 GB of RAM, 4cores, with the same versions of the programs - VS, windows XP ...- installed in the 8cores machine).
I was wondering if the double-quad core architecture could generate some problems.
Moreover, a simple line of plotting on a file of some values located in a subroutine, generates differences (not truncating errors, but completely different values) in all the versions (debug/release, win32/x64, different machines).
however, main results, apart from truncating errors, look very similar.
Any suggestions?
Thanks
gattorognoso
0 Kudos
2 Replies
Steven_L_Intel1
Employee
565 Views
Would I be correct in assuming that the problem you are having is in running the program, not building it? What do you mean by "the code stops"? Do you get an error message?

Does this program use parallel programming features (OpenMP. etc.?) The processor configuration itself should not be an issue, but if you have a multithreaded program that is not properly coded, errors can be difficult to find. The Intel Thread Checker can be useful here.
0 Kudos
Intel_C_Intel
Employee
565 Views

I am not specialist and might be wrong but you can check Project -Property All Configurations Optimization Optimization for Intel Processor or something like this. If you sure that your code dont have any bug.

0 Kudos
Reply