Re: bug with ifort + openmp : allocatable array not allocated after allocation
- From: Steve Lionel <Steve.Lionel@xxxxxxxxxxxxx>
- Date: Mon, 07 Jul 2008 10:22:21 -0400
On Fri, 4 Jul 2008 12:18:23 -0700 (PDT), Domel <domel07@xxxxxxxxx> 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.
--
Steve Lionel
Developer Products Division
Intel Corporation
Nashua, NH
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
.
- Follow-Ups:
- References:
- Prev by Date: Re: public comment on fortran 2008
- Next by Date: Re: Best way to allocate array within subroutine
- Previous by thread: Re: bug with ifort + openmp : allocatable array not allocated after allocation
- Next by thread: Re: bug with ifort + openmp : allocatable array not allocated after allocation
- Index(es):
Relevant Pages
|
|
