[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gcc-fortran
Subject:    [Fwd: GCC 4.2.1 Status Report (2007-05-28)]
From:       Brooks Moses <brooks.moses () codesourcery ! com>
Date:       2007-05-29 5:26:06
Message-ID: 465BB96E.60508 () codesourcery ! com
[Download RAW message or body]

This was recently posted on the main GCC list; I'm forwarding it for 
those of us who only read the Fortran list.

- Brooks


-------- Original Message --------
Subject: GCC 4.2.1 Status Report (2007-05-28)
Date: Mon, 28 May 2007 15:48:39 -0700
From: Mark Mitchell <mark@codesourcery.com>
To: GCC <gcc@gcc.gnu.org>
Newsgroups: gmane.comp.gcc.devel

I would like to try to keep the GCC 4.2.x release branch on the
time-driven release cycle for point releases that is part of the GCC
development plan.  I left an embarrassing gap in the GCC 4.1.x release
cycle, and I plan to avoid that mistake for GCC 4.2.x.

Therefore, I plan to make the GCC 4.2.1 release on or about July 13th.
As with the 4.2.0 release, I will be most concerned about P1 regressions
in 4.2.x, not present in 4.1.x.  At present, that looks to be:

* PR 30252 miscompilation of sigc++-2.0 based code with -fstrict-aliasing

* PR 31360 rtl loop invariant is broken

This is a missed-optimization problem, fixed on the mainline -- although
the audit trail suggests that there are unresolved problems on ARM,
including bad code generation and CSiBE regressions.

There are currently 128 P3-and-higher regressions from previous GCC
releases that apply to the 4.2 branch.

In order to actually make the release July 13th, I've put a note in my
calendar to make 4.2.1 RC1 on July 1st.  If there are 4.2.x regressions
that you're interested in fixing, please do your best to fix them by
that date.

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713


[prev in list] [next in list] [prev in thread] [next in thread]