Re: GCC 4.7.3 Status Report (2013-04-03)

2013-04-04 Thread Richard Biener
On Thu, 4 Apr 2013, Jack Howarth wrote: > On Wed, Apr 03, 2013 at 03:23:36PM +0200, Richard Biener wrote: > > > > Status > > == > > > > The GCC 4.7 branch is ready for a release candidate of GCC 4.7.3 > > which I will do tomorrow if no serious issue shows up until then. > > The branch is fro

Re: GCC 4.7.3 Status Report (2013-04-03)

2013-04-04 Thread Jack Howarth
On Wed, Apr 03, 2013 at 03:23:36PM +0200, Richard Biener wrote: > > Status > == > > The GCC 4.7 branch is ready for a release candidate of GCC 4.7.3 > which I will do tomorrow if no serious issue shows up until then. > The branch is frozen now, all changes require release manager approval > u

Re: GCC 4.7.3 Status Report (2013-04-03)

2013-04-03 Thread Joel Sherrill
On 4/3/2013 8:36 AM, Richard Biener wrote: On Wed, 3 Apr 2013, Joel Sherrill wrote: The RTEMS Community would like to squeeze pr56771 in. It only got a fix in the past few days. It is a one line arm-rtems specific path to libcpp configure. Can I commit that? Sure, if it got RTEMS maintainer

Re: GCC 4.7.3 Status Report (2013-04-03)

2013-04-03 Thread Richard Biener
On Wed, 3 Apr 2013, Joel Sherrill wrote: > The RTEMS Community would like to squeeze pr56771 in. It only got a fix in > the past few days. It is a one line arm-rtems specific path to libcpp > configure. > > Can I commit that? Sure, if it got RTEMS maintainer approval. Richard. > --joel > RTE

Re: GCC 4.7.3 Status Report (2013-04-03)

2013-04-03 Thread Joel Sherrill
The RTEMS Community would like to squeeze pr56771 in. It only got a fix in the past few days. It is a one line arm-rtems specific path to libcpp configure. Can I commit that? --joel RTEMS Richard Biener wrote: Status == The GCC 4.7 branch is ready for a release candidate of GCC 4.7.3 wh