Intel compiler V11 and OpenMP - problem

tim18
Total Points:
66,417
Status Points:
66,417
Black Belt
November 21, 2008 8:44 AM PST
Rate
 
#4 Reply to #3
Quoting - FDSUser

I have tried this, but it has no effect. The problem occurs at the same line in the code. Furthermore this could be no solution, because if the variables are correctly implemented in a serial version of the code, there should be no changes in the OpenMP code version. If I have to check all the variables, parallelization would be very difficult, becuase the code has more than 50.000 lines and more than 500 variables.

If it is helpful, I could submit the complete code.

The -openmp option should make local arrays dynamic, even if they were not already automatic (in the standard Fortran sense) by definition, so the lack of change is to be expected.  The problem usually cited with Fortran automatic arrays is the lack of error diagnosis.  Supposing the allocation fails, which might happen simply because the stack size limit is reached at this point, you don't have a satisfactory way to catch it.  Hence the usual recommendation for ALLOCATABLE arrays with STAT= checking.  This would apply equally to the serial version, but the OpenMP version will consume more stack.



Intel Software Network Forums Statistics

8290 users have contributed to 31236 threads and 99111 posts to date.
In the past 24 hours, we have 7 new thread(s) 20 new posts(s), and 30 new user(s).

In the past 3 days, the most popular thread for everyone has been comparison cilk++, openmp, pthreads first results The most posts were made to comparison cilk++, openmp, pthreads first results The post with the most views is Very amusing...  Escalated as

Please welcome our newest member zq.x