This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC 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: GCC 4.3.3 Status Report (2009-01-17), branch frozen for release


On Fri, 16 Jan 2009, H.J. Lu wrote:

> On Fri, Jan 16, 2009 at 3:03 PM, Richard Guenther <rguenther@suse.de> wrote:
> >
> > It's not my turn to send a status report, but as I plan doing a release
> > candidate for GCC 4.3.3 soon I thought a status report for that would
> > be in order.
> >
> > Status
> > ======
> >
> > The GCC 4.3 branch is now frozen in preparation for a release candidate
> > for the GCC 4.3.3 release.  When the branch is unfrozen again I will
> > send a message stating so.  All checkins to the branch require approval
> > by a release manager now.
> >
> > There is a single regression that shows up as P1, but as it is not
> > a regression on the branch (but from the tree-ssa merge) it does not
> > block the GCC 4.3.3 release (but the bug priority is considered the priority
> > for the newest release the bug is a regression for).
> >
> > I am not aware of any issues blocking an immediate release of GCC 4.3.3.
> > Please make me aware of such issues by replying to this mail and/or
> > by CCing me on bugzillas that are regressions on the GCC 4.3 branch
> > but are not marked as such (a regression on the GCC 4.3 branch is a
> > bug with a testcase that worked in a previous GCC 4.3 based release
> > but fails on the top of the GCC 4.3 branch).
> >
> 
> I think
> 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38877
> 
> also happens on 4.3 branch.

Thanks for noticing, that bug had the wrong target milestone and thus
didn't appear in the 4.3 regression list.

Richard.


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