bug with ifort + openmp : allocatable array not allocated after allocation

[commbank]

Hi Steve,

Below is a response to a bug question posted by someone and replied by you on7/7/2008 10:22:21 PM

at: http://fortran.itgroups.info/69/2/thread-1900153.html

I could not find this thread in this forum so I am reposting it - basically to ask what is the progress on this issue. The post below is 2008 but I am still getting this error with OpenMP and iFort and thanks Steve your workaround still works. However, has Intel fixed this in the latest compiler yet? I am using one version behind which is 11.0.074.

Thanks

Clinton

---------------------------------------------------------------------------

TITLE: "bug with ifort + openmp : allocatable array not allocated after allocation "

On Fri, 4 Jul 2008 12:18:23 -0700 (PDT), Domel wrote:

>The following code should allocate an allocatable shared array inside
>the parallel construct using SINGLE clause. It generates a run time
>error with ifort 10.1:
>
>forrtl: severe (408): fort: (8): Attempt to fetch from allocatable
>variable USEDD when it is not allocated

I can reproduce this bug - it happens only if you ask for the optional
"pointer checking" feature (-check pointer, implicit in -C) as well as OpenMP.
The array actually is allocated but the code that is triggered by the pointer
checking feature is evidently looking in the wrong place. We'll fix it.

The workaround is to not use the -check pointer feature.
For email address, replace "invalid" with "com"

User communities for Intel Software Development Products
http://softwareforums.intel.com/
Intel Fortran Support
http://support.intel.com/support/performancetools/fortran
My Fortran blog
http://www.intel.com/software/drfortran

[Steven_L_Intel1]

That post you found was actually from the comp.lang.fortran newsgroup. I won't be able to check it until tomorrow, but I'm fairly certain that bug is fixed in the current 11.1 release (11.1 Update 6). If I can locate the specific bug entry, I can get more detail.

[Steven_L_Intel1]

This was issuse DPD200047400, fixed in 11.1.