[Patch, Fortran] OOP: merging fortran-dev to trunk?

[Richard Guenther]

On Mon, Nov 30, 2009 at 5:42 PM, Tobias Burnus <burnus@net-b.de> wrote:
> On 11/30/2009 03:32 PM, Janus Weil wrote:
>> My proposal would be to merge the current state of fortran-dev to the
>> trunk now, and leave the advanced TBP stuff that Paul is working on
>> for 4.6
>>
>
> The patch is OK from my side, after browsing through the patch.
> (Reasoning: The changes are limited to the OOP part of gfortran which is
> new and the patch fix some bugs with OOP exposed by-real-world program.
> (5 days ago, graphite saw a similarly large branch-to-trunk merge.) I
> also discussed with Daniel K. on IRC and he was also in favour of merging.)
>
> Can you check after committal what changes are needed at
> http://gcc.gnu.org/gcc-4.5/changes.html ? Do we need larger warnings
> about non-working parts? Or should be things marked as working which
> weren't before?
>
>  * * *
>
> General gfortran status:
> * No known regression
> * 8 such-marked F95 PRs
> * 35 wrong-code PRs (some have only a very low priority)
> * 85 wrong-code/ice-on-valid/rejects-valid PRs (ditto)
> * 455 PRs in total (several of them enhancement/feature requests)

Note that all fortran frontend regressions are marked P4 or P5
as fortran is not release critical.  For non-regression bugs the
priority is irrelevant and generally not set (thus P3).

Richard.