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

Access violation - formerly "okay" - okay in other compilers.

lklawrie
Beginner
‎02-21-2008 05:18 AM
586 Views

For some reason, IVF (10.1.14) has decided that the first assignment in the below is an access violation:

Allocate(MultizoneSurfaceStdConditionsCrackData(0))
=> MultizoneSurfaceStdConditionsCrackData(0)%Name='*'
MultizoneSurfaceStdConditionsCrackData(0)%StandardT=20.d0
MultizoneSurfaceStdConditionsCrackData(0)%StandardP=101325.d0
MultizoneSurfaceStdConditionsCrackData(0)%StandardW=0.0d0

I have fixed it (for now) by:

Allocate(MultizoneSurfaceStdConditionsCrackData(0:1))

But am wondering why. CVF likes it. g95 likes it.

Linda

0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎02-21-2008 05:37 AM
586 Views
I wonder why CVF and g95 like it. You allocated the array with bounds (1:0) which means it is empty.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.