On Wed, May 17, 2017 at 7:13 AM, Andi Kleen wrote:
> On Tue, May 16, 2017 at 08:40:02PM -0700, Andrew Pinski wrote:
>> On Tue, May 16, 2017 at 7:16 PM, Andi Kleen wrote:
>> > From: Andi Kleen
>> >
>> > When running creduce on an ICE substantial amounts of the total
>> > CPU time go to backtrace_
On Tue, May 16, 2017 at 08:40:02PM -0700, Andrew Pinski wrote:
> On Tue, May 16, 2017 at 7:16 PM, Andi Kleen wrote:
> > From: Andi Kleen
> >
> > When running creduce on an ICE substantial amounts of the total
> > CPU time go to backtrace_qsort() (sorting dwarf of the compiler) for
> > printing th
On 2017.05.16 at 19:16 -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> When running creduce on an ICE substantial amounts of the total
> CPU time go to backtrace_qsort() (sorting dwarf of the compiler) for
> printing the backtrace of the ICE. When running a reduction we don't need the
> backtrace
On Tue, May 16, 2017 at 7:16 PM, Andi Kleen wrote:
> From: Andi Kleen
>
> When running creduce on an ICE substantial amounts of the total
> CPU time go to backtrace_qsort() (sorting dwarf of the compiler) for
> printing the backtrace of the ICE. When running a reduction we don't need the
> backtr
On Tue, May 16, 2017 at 7:16 PM, Andi Kleen wrote:
> From: Andi Kleen
>
> When running creduce on an ICE substantial amounts of the total
> CPU time go to backtrace_qsort() (sorting dwarf of the compiler) for
> printing the backtrace of the ICE. When running a reduction we don't need the
> backtr