On 11/24/2016 10:09 AM, Jakub Jelinek wrote:
> On Thu, Nov 24, 2016 at 09:51:49AM +0100, Richard Biener wrote:
>> On Thu, Nov 24, 2016 at 9:36 AM, Jakub Jelinek wrote:
>>> On Thu, Nov 24, 2016 at 09:26:25AM +0100, Richard Biener wrote:
> Alternately, given all the problems we have with this ki
On Thu, Nov 24, 2016 at 09:51:49AM +0100, Richard Biener wrote:
> On Thu, Nov 24, 2016 at 9:36 AM, Jakub Jelinek wrote:
> > On Thu, Nov 24, 2016 at 09:26:25AM +0100, Richard Biener wrote:
> >> > Alternately, given all the problems we have with this kind of problem, we
> >> > should seriously consi
On Thu, Nov 24, 2016 at 9:36 AM, Jakub Jelinek wrote:
> On Thu, Nov 24, 2016 at 09:26:25AM +0100, Richard Biener wrote:
>> > Alternately, given all the problems we have with this kind of problem, we
>> > should seriously consider throttling back what we consider an error during
>> > a
>> > profil
On Thu, Nov 24, 2016 at 09:26:25AM +0100, Richard Biener wrote:
> > Alternately, given all the problems we have with this kind of problem, we
> > should seriously consider throttling back what we consider an error during a
> > profiled bootstrap. This kind of stuff is a maintenance nightmare with
On Wed, Nov 23, 2016 at 7:33 PM, Jeff Law wrote:
> On 11/23/2016 09:13 AM, Martin Liška wrote:
>>
>> Hello.
>>
>> As described in the PR, the patch fixes profiled bootstrap on
>> x86_64-linux-gnu.
>>
>> Patch can bootstrap on ppc64le-redhat-linux and survives regression tests.
>> And
>> profiled b
On 11/23/2016 09:13 AM, Martin Liška wrote:
Hello.
As described in the PR, the patch fixes profiled bootstrap on x86_64-linux-gnu.
Patch can bootstrap on ppc64le-redhat-linux and survives regression tests. And
profiled bootstrap on x86_64-linux-gnu finishes successfully.
Ready to be installed?
