[Fwd: GCC 4.4.0 Status Report (2008-08-08)]

[Paul Richard Thomas]

Tobias,

I am up to my eyeballs, preparing the house in France to rent and
getting ready to move with my family to Spain.  Whilst I have made a
start on regenerating the CLASS and SELECT TYPE patch, I will be hard
put to get it ready by the end of August.  Since it will only be
available for -std=f2003, I wonder if I could have a few more weeks?
I suspect that Daniel and Janus will need some extra time too:-)

I have realised that the first implementation of OOP will have to be
very limited.  Not only will it be pushing things to get dynamic
dispatch working but, I realise now, the f2k allocate by type and
scalar allocation will have to be implemented to get the full
functionality.  The allocate by type makes allocatable classes useful
- otherwise, one can only produce the declared type for class
allocation.  Scalar allocation is needed for the reasons that Richard
Maine has underlined and for scalar class objects per se.  In addition
automatic deallocation of allocatable objects is going to be a must.

Therefore, since we are progressing quite well on F2K features, I
rather suspect that gfortran-4.5 is going to be something of a quantum
leap.

That said, I am very aware that some months of bug bashing is very
necessary and that we'll all have to work our pretty little cotton
socks off to get the number of PRs down.

Cheers

Paul

On Sun, Aug 10, 2008 at 5:41 PM, Tobias Burnus <burnus@net-b.de> wrote:
> Stage3 will start end of August.
>
> Tobias
>
> Status
> ======
>
> It's time to start moving GCC 4.4.0 towards a release, with a release
> target date in Q4 2008 or Q1 2009.  We have had an extraordinarily long
> Stage 1 in order to allow development of a variety of important
> functionality, including the IRA register allocator, tuples, the
> Graphite loop optimization functionality, and many other important
> projects.  Most of these are either done, or appear to be nearing
> conclusion.  So, we've got plenty of new functionality, and it's time to
> start driving towards a release.
>
> Therefore, Jakub, Joseph, Richard, and I have decided to close Stage 1
> as of August 31st, 2008.  We will at that point go directly to Stage 3,
> during which time only bug fixes will be accepted.  That means that all
> new features must be submitted prior to August 31st.  Any exceptions to
> this policy will be made on a case-by-case basis by consensus of the RMs.
>
> If you're a maintainer, please help to review outstanding new-feature
> patches before this time, so that we are as feature-complete as possible
> by September 1st.  Traditionally, Stage 3 has been scheduled for two
> months, but, as for past releases, we will probably stay until Stage 3
> until we feel that we have reached a sufficiently low bug count to merit
> going to the final regression-only stage.
>
> Quality Data
> ============
>
> Priority          #     Change from Last Report
> --------        ---     -----------------------
> P1               13
> P2              119
> P3                2
> --------        ---     -----------------------
> Total           134     So long ago it doesn't matter
>
> This is a reasonably good situation to be in at this point.  Of course,
> as further testing is performed we are likely to see a variety of issues.
>
> As much of the functionality in 4.4 is aimed at optimization, we need to
> be particularly sensitive to performance issues.  If our benchmark
> numbers aren't improved relative to the previous release, or if we've
> increased code size when compiling with -Os, then we've got a problem.
> Some of those issues will probably be difficult to fix.
>
> Previous Report
> ===============
>
> http://gcc.gnu.org/ml/gcc/2008-04/msg00539.html
>
> Next Report
> ===========
>
> The next report for 4.4.0 will be sent by Richard.
>
> --
> Mark Mitchell
> CodeSourcery
> mark@codesourcery.com
> (650) 331-3385 x713
>
>
>



-- 
The knack of flying is learning how to throw yourself at the ground and miss.
 --Hitchhikers Guide to the Galaxy