On Wed, Nov 25, 2015 at 7:59 PM, David Edelsohn wrote:
> On Wed, Nov 25, 2015 at 11:57 AM, Paolo Bonzini 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 configu
On Wed, Nov 25, 2015 at 11:57 AM, Paolo Bonzini 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 t
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 fi
On Sun, Nov 22, 2015 at 8:38 AM, Paolo Bonzini wrote:
>
>
> On 20/11/2015 14:14, David Edelsohn wrote:
>> On Fri, Nov 20, 2015 at 7:53 AM, Richard Biener wrote:
>>>
>>> Status
>>> ==
>>>
>>> We plan to do a GCC 5.3 release candidate at the end of next week
>>> followed by the actual release a
On 20/11/2015 14:14, David Edelsohn wrote:
> On Fri, Nov 20, 2015 at 7:53 AM, Richard Biener 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 regress
On Fri, Nov 20, 2015 at 7:53 AM, Richard Biener 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 thin
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
