This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Fwd: GCC 4.7.0 Status Report (2011-11-08), Stage 1 is over, Stage 3 in effect immediately
- From: Tobias Burnus <burnus at net-b dot de>
- To: gfortran <fortran at gcc dot gnu dot org>
- Date: Tue, 08 Nov 2011 16:03:52 +0100
- Subject: Fwd: GCC 4.7.0 Status Report (2011-11-08), Stage 1 is over, Stage 3 in effect immediately
- References: <20111108112924.GE17997@tyan-ft48-01.lab.bos.redhat.com>
For the general status, see below. For Fortran:
IRC meeting: I propose we do another meeting on Sunday, 20 November at
the usual time: 21:00 (9pm) CET, 20:00 (8pm) UTC, 12:00 (noon) PST - as
usual at IRC.Oftc.net's #gfortran channel. Topic: What to do in Stage 3
and beyond. (Beyond could be which F2003/F2008/TS29113 feature in 4.8,
array-descriptor reform, funding etc. You can also ask about GSoC Mentor
Meeting, if you want.)
Stage 1 items:
* The 66 scalarizer patches have been committed to the trunk and seem to
work flawlessly. A big thanks goes to Mikael.
* The constructor patch was finally submitted, but still needs to be
reviewed.
* The last version of the polymorphic arrays patch has to be still
submitted, though this patch is less invasive and thus still fits as
(Stage 1 + Stage 3)/2 patch.
On the bug front, the situation looks rather bright except for the 3
(well, 4) 4.7-only regressions and for the reject-valid/wrong-code PRs
50981 and 50684.
Regressions (9 marked as Fortran regressions) and failures (3 - half of
them Fortran bugs):
* gfortran.dg/select_type_12.f03 (P1 regression, PR middle-end/50640).
Fixable at front-end level by pushing both the vtable declaration and
the _copy-function declaration to the top level.
* gfortran.fortran-torture/execute/entry_4.f90 (P1 regression, PR
middle-end/50628)
* gfortran.dg/realloc_on_assign_5.f03 (never worked, PR fortran/47674).
The issue is a missing temporary.
* PR 50981 (4.4-4.7) wrong-code with elemental scalarizing and absent
arguments
* PR 50923 (4.4-4.7) no warning that the function result var is not set
* PR 50690 (4.7) ICE-on-valid with FE optimization and OpenMP workshare.
Thomas has posted a draft patch, which needs to be refined.
* PR 50684 (4.6/4.7) Rejects valid in MOVE_ALLOC (pointer-intent issue)
* PR 42954 (4.4-4.7) TARGET_*_CPP_BUILTINS issue. Anyone wanting to
patch ~14 targets?
* PR 50410 (4.6/4.7) ICE in record reference - mixing DATA and explicit
initialization
* PR 50105 (4.6/4.7) I/O too small field "** " vs. "******"
* PR 50016 (4.7) I/O performance issues due to _commit on MinGW(32,64).
Janne has a patch
* PR 49791 (4.4-4.7) I/O: Extended array read (vendor extension) still
fails in a special case.
I think we also have a bit more than half a dozen tiny, smaller, and
medium-large sized patches, which need to be reviewed. Or, which need to
be fixed and reposted.
(During Stage 3, I would like to see fixes to deferred-length
(allocatable length) character variables, some OOP fixes, and a fix for
the last two [single-image] coarray issues - polymorphic coarrays and
disabling realloc of coarray components for intrinsic assignment.)
Tobias
-------- Original Message --------
Subject: GCC 4.7.0 Status Report (2011-11-08), Stage 1 is over, Stage 3
in effect immediately
Date: Tue, 8 Nov 2011 00:29:25 -1100
From: Jakub Jelinek
Status
======
The GCC trunk is now in stage3, even TM branch has been merged
during the last minute, patches submitted during stage1
may be still accepted, if they don't need significant rewrites,
but please try to get them in soon. Otherwise only bugfixes
and documentation fixes are allowed for the trunk.
If all goes well, stage3 would again as last time go on for roughly
two months, with the aim of getting the release at the end of
March to mid April.
We have accumulated quite a lot of bugs during the almost 8 months
long stage 1, please help with analysing them and bugfixing.
Quality Data
============
Priority # Change from Last Report
-------- --- -----------------------
P1 46 + 15
P2 99 - 10
P3 24 - 4
-------- --- -----------------------
Total 169 + 1
Previous Report
===============
http://gcc.gnu.org/ml/gcc/2011-10/msg00481.html
The next report will be sent by Joseph.