This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [Fwd: Question on PR25289]
- From: FX Coudert <fxcoudert at gmail dot com>
- To: Jerry DeLisle <jvdelisle at verizon dot net>
- Cc: Thomas Koenig <Thomas dot Koenig at online dot de>, Fortran List <fortran at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>, Steve Kargl <sgk at troutmask dot apl dot washington dot edu>
- Date: Thu, 13 Jul 2006 08:39:15 +0200
- Subject: Re: [Fwd: Question on PR25289]
- References: <44B45D28.2090106@verizon.net> <20060712102321.GA5440@meiner.onlinehome.de> <44B5B97B.1060809@verizon.net>
At this point I propose we commit the patch to 4.2 and allow some
exposure to see if there are any real problems. We can then always fix
or revert if something shows up.
Is this not why trunk is not a release yet?
Well, it's supposed to be frozen under release-branch rules for some
time, to allow it to stabilize. Even if we (Fortran front-end
developers) do not always follow strcitly these rules, there is
something to it.
I'm all for thinking and testing, and don't really like the "let's try
it anyhow" approach :) Moreover, to be in complete coherence with this
opinion, I'll quickly (before monday) review your patch if you send it
once more, in its final version (I somehow got the older messages in
this thread lost).
FX