This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [patch] Fix fortran/25031, multiple allocations

From: Brooks Moses <bmoses at stanford dot edu>
To: gcc-patches at gcc dot gnu dot org
Cc: fortran at gcc dot gnu dot org
Date: Wed, 01 Mar 2006 18:03:26 -0800
Subject: Re: [patch] Fix fortran/25031, multiple allocations
References: <20060301204022.GA7356@meiner.onlinehome.de> <20060302003512.GA65731@troutmask.apl.washington.edu>

Steve Kargl wrote:

On Wed, Mar 01, 2006 at 09:40:22PM +0100, Thomas Koenig wrote:

here is a fix for PR 25031.  The problem here was that we used
to be capable of allocating an allocatable array twice without
intermediate deallocation, which should raise an error.

Are you saying that this program should fail?

program a
  real, allocatable :: x(:)
  allocate(x(4))
  allocate(x(3))
end program a

F95 Draft Standard, 6.3.1.1: "An allocatable array that has been allocated by an ALLOCATE statement and has not been subsequently deallocated (6.3.3) is *currently allocated* and is definable. Allocating a currently allocated allocatable array causes an error condition in the ALLOCATE statement." (emphasis in original)

- Brooks

Follow-Ups:
- Re: [patch] Fix fortran/25031, multiple allocations
  - From: Steve Kargl

References:
- [patch] Fix fortran/25031, multiple allocations
  - From: Thomas Koenig
- Re: [patch] Fix fortran/25031, multiple allocations
  - From: Steve Kargl

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]