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

2013 SP 1 Compiler Error with OpenMP

Allen_Barnett
Beginner
860 Views

Hi: We upgraded to XE 2013 SP 1 and our main code now crashes when trying to access an allocatable array. The array was apparently not allocated successfully even though the STAT variable (as in ALLOCATE( array(12), STAT=ios)) says the allocation is successful. I've tried to simplify the code and have attached a little example problem which seems to reproduce the issue. The problem arises when compiling with OpenMP active. Building the program with OpenMP OFF yields a successful run; turning it ON causes an ALLOCATE to fail without setting the STAT variable. A successful run should say:

> driver.exe
 ONAME allocation succeeded
 Output should be "a" on a line and "b" on the next line
 a                                                               
 b                                                               

The failed run shows:

> driver_omp.exe
 ONAME allocation succeeded
 Output should be "a" on a line and "b" on the next line
 Hmm. ONAME wasn't allocated???

Furthermore, the routine with the OpenMP commands is not even being invoked.

Interestingly, I get the same result both on windows with 14.0.0.103 Build 20130728 and on linux with 14.0.0.080 Build 20130728. The example program works correctly both with and without OpenMP when compiled with 13.1.0.149 Build 20130118 (on windows).

Thanks,
Allen

0 Kudos
7 Replies
Steven_L_Intel1
Employee
860 Views

Thanks, we'll take a look.

0 Kudos
Allen_Barnett
Beginner
860 Views

Hi: Were you able to reproduce my problem?

Thanks,
Allen

0 Kudos
Steven_L_Intel1
Employee
860 Views

Yes, I could. We are still investigating.

0 Kudos
Allen_Barnett
Beginner
860 Views

OK. Thanks for the response.

0 Kudos
Steven_L_Intel1
Employee
860 Views

Escalated as issue DPD200248411. Curiously, /Qopenmp_stubs doesn't trigger the problem.

0 Kudos
Steven_L_Intel1
Employee
860 Views

It looks as if this got fixed in Update 2.

0 Kudos
Allen_Barnett
Beginner
860 Views

Yes. Update 2 is solves all our problems. Thanks!

0 Kudos
Reply