This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran 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: PR31711 - rhs array is changed while assiging to same lhs array

From: Brooks Moses <brooks dot moses at codesourcery dot com>
To: Paul Richard Thomas <paul dot richard dot thomas at gmail dot com>, "fortran at gcc dot gnu dot org List" <fortran at gcc dot gnu dot org>
Cc: Thomas Koenig <tkoenig at alice-dsl dot net>
Date: Sat, 28 Apr 2007 01:03:24 -0700
Subject: Re: PR31711 - rhs array is changed while assiging to same lhs array
References: <339c37f20704280029s43d07d6du43c2b491f95c0a05@mail.gmail.com> <1177746307.3165.5.camel@meiner.onlinehome.de>

Thomas Koenig wrote:

What should we do about 4.2? Is it too late?
IMHO, both this fix and the fix for PR 31196 should go into 4.2, but we
need Mark's approval.

Do we?

This is a fix for a regression, and the 4.2 branch is not currently frozen. The rules for non-frozen release branches permit regression fixes; thus, I'm fairly sure that this is quite explicitly permitted.

(If it's not permitted, I've been doing something wrong, since I was relying earlier today on the fact that those same rules permitted documentation changes on release branches....)

As I understand it, it's only non-regression fixes, like the one for PR31196 that you also mention, that require explicitly asking Mark's permission.

- Brooks

Follow-Ups:
- Re: PR31711 - rhs array is changed while assiging to same lhs array
  - From: Thomas Koenig

References:
- PR31711 - rhs array is changed while assiging to same lhs array
  - From: Paul Richard Thomas
- Re: PR31711 - rhs array is changed while assiging to same lhs array
  - From: Thomas Koenig

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