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: Gfortran 4.3 projects


i once again apologize for the delay; there appears to be a delay with my 
paperwork and we're trying to get it all worked out.  approximately how 
long before 4.2 freezes?

Thanks.
Chris

On Mon, 25 Sep 2006, Steve Kargl wrote:

> On Wed, Sep 20, 2006 at 10:39:51AM -0600, Christopher D. Rickett wrote:
> > 
> > > 
> > > By the way, I had the following question about the ISO_BINDING_C patch
> > > for Christopher and Steve: if I understood correctly, you intend to
> > > commit it as a "preview" in 4.2, since it doesn't change other parts
> > > of the code. What will be the status of it, from the maintaining point
> > > of view? Will ISO_BINDING_C patches be backported from 4.3 to 4.2 or
> > > not?
> > 
> > i don't know about the backporting question, but as far as maintaining, i 
> > do plan on continuing work on it after i submit it so i'll be 
> > around for bugs that come up.  i do plan on working more on the procedure 
> > decl stmt's, which i've started (very simple versions of them work right 
> > now), but the bigger part of it is to allow the pointer attribute for 
> > procedure decl variables.  
> > 
> > yesterday, i made dejagnu tests out of more of my test cases, so now the 
> > main tests that i have not added are those that test gfortran's abilities 
> > for catching errors.  with my latest tests added, there are no unexpected 
> > failures when i do 'make check-gfortran'.  
> > 
> > we've been trying to get ahold of the FSF person that is in charge of my 
> > paperwork, but have been unable to.  we'd like to know if they received 
> > the paperwork, and if they approve it.  i'll try again today.
> > 
> > i apologize this is taking so long..  i'd like to see this get previewed 
> > in 4.2.
> > 
> 
> My intentions are to help integrate Chris' patch into the tree.
> If he (or more likely the patch) is not ready by the time 4.2 is
> branched, then it will be a 4.3 feature.  Backporting shouldn't
> be an issue if the patch is reasonably self contained.  OTOH,
> if the patch is only present in 4.3, then Chris does not have to
> track bugs in two different branchs.  I'll discuss a back port
> with Chris if that is direction gfortran goes.
> 
> -- 
> Steve
> 


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