GCC 5.3 Status Report (2015-11-20)

GCC 5.3 Status Report (2015-11-20)

[Richard Biener]

Status
======

We plan to do a GCC 5.3 release candidate at the end of next week
followed by the actual release a week after that.

So now is the time to look at your regression bugs in bugzilla and
do some backporting for things already fixed on trunk.


Quality Data
============

Priority          #   Change from last report
--------        ---   -----------------------
P1                0
P2              121    +  30
P3               20    -   8
P4		 87    +   2
P5		 32    +   2
--------        ---   -----------------------
Total P1-P3     141    +  22
Total		260    +  24


Previous Report
===============

https://gcc.gnu.org/ml/gcc/2015-07/msg00197.html

Re: GCC 5.3 Status Report (2015-11-20)

[David Edelsohn]

On Fri, Nov 20, 2015 at 7:53 AM, Richard Biener <rguenther@suse.de> wrote:
>
> Status
> ======
>
> We plan to do a GCC 5.3 release candidate at the end of next week
> followed by the actual release a week after that.
>
> So now is the time to look at your regression bugs in bugzilla and
> do some backporting for things already fixed on trunk.

I'm still waiting for approval of the libtool change to support AIX
TLS symbols (PR 68192).  There has been no response on Libtool patches
mailing list.

I again request permission to apply the patches to GCC trunk and 5-branch.

Thanks, David

Re: GCC 5.3 Status Report (2015-11-20)

[Paolo Bonzini]

On 20/11/2015 14:14, David Edelsohn wrote:
> On Fri, Nov 20, 2015 at 7:53 AM, Richard Biener <rguenther@suse.de> wrote:
>>
>> Status
>> ======
>>
>> We plan to do a GCC 5.3 release candidate at the end of next week
>> followed by the actual release a week after that.
>>
>> So now is the time to look at your regression bugs in bugzilla and
>> do some backporting for things already fixed on trunk.
> 
> I'm still waiting for approval of the libtool change to support AIX
> TLS symbols (PR 68192).  There has been no response on Libtool patches
> mailing list.
> 
> I again request permission to apply the patches to GCC trunk and 5-branch.

Let me look around for a libtool committer tomorrow, I'll get back to you.

Paolo

Re: GCC 5.3 Status Report (2015-11-20)

[David Edelsohn]

On Sun, Nov 22, 2015 at 8:38 AM, Paolo Bonzini <bonzini@gnu.org> wrote:
>
>
> On 20/11/2015 14:14, David Edelsohn wrote:
>> On Fri, Nov 20, 2015 at 7:53 AM, Richard Biener <rguenther@suse.de> wrote:
>>>
>>> Status
>>> ======
>>>
>>> We plan to do a GCC 5.3 release candidate at the end of next week
>>> followed by the actual release a week after that.
>>>
>>> So now is the time to look at your regression bugs in bugzilla and
>>> do some backporting for things already fixed on trunk.
>>
>> I'm still waiting for approval of the libtool change to support AIX
>> TLS symbols (PR 68192).  There has been no response on Libtool patches
>> mailing list.
>>
>> I again request permission to apply the patches to GCC trunk and 5-branch.
>
> Let me look around for a libtool committer tomorrow, I'll get back to you.

Any progress?

Thanks, David

Re: GCC 5.3 Status Report (2015-11-20)

[Paolo Bonzini]

On 24/11/2015 16:57, David Edelsohn wrote:
> > > We plan to do a GCC 5.3 release candidate at the end of next week
> > > followed by the actual release a week after that.
> > >
> > > So now is the time to look at your regression bugs in bugzilla and
> > > do some backporting for things already fixed on trunk.
> >
> > I'm still waiting for approval of the libtool change to support AIX
> > TLS symbols (PR 68192).  There has been no response on Libtool patches
> > mailing list.
> >
> > I again request permission to apply the patches to GCC trunk and 5-branch.
> >
> > Let me look around for a libtool committer tomorrow, I'll get back to you.
>
> Any progress?

Patch committed to upstream libtool, thanks for your understanding.

Paolo

Re: GCC 5.3 Status Report (2015-11-20)

[David Edelsohn]

On Wed, Nov 25, 2015 at 11:57 AM, Paolo Bonzini <bonzini@gnu.org> wrote:

> Patch committed to upstream libtool, thanks for your understanding.

Great!

How can I have the patch backported to GCC trunk and 5-branch libtool,
and then rebuild configure with the appropriate versions of autoconf?
I have not been able to install the correct versions of autoconf to
produce configure without gratuitous changes.

Thanks, David

Re: GCC 5.3 Status Report (2015-11-20)

[Richard Biener]

On Wed, Nov 25, 2015 at 7:59 PM, David Edelsohn <dje.gcc@gmail.com> wrote:
> On Wed, Nov 25, 2015 at 11:57 AM, Paolo Bonzini <bonzini@gnu.org> wrote:
>
>> Patch committed to upstream libtool, thanks for your understanding.
>
> Great!
>
> How can I have the patch backported to GCC trunk and 5-branch libtool,
> and then rebuild configure with the appropriate versions of autoconf?
> I have not been able to install the correct versions of autoconf to
> produce configure without gratuitous changes.

I've never had problems building the FSF tarballs of the versions we use
and using those to re-generate files.  Sometimes it shows others
re-generated with slightly different versions (thus producing unrelated
changes) though.

I originally planned to do RC1 tomorrow (Friday) but if I don't see any
traces of this patch I'll wait until Monday but no longer.

Thanks,
Richard.

> Thanks, David