Re: [PATCH] dwarf2cfi: Dump row differences before asserting

2016-11-10 Thread Jakub Jelinek
On Thu, Nov 10, 2016 at 11:29:12AM -0600, Segher Boessenkool wrote: > Ping. > > On Mon, Oct 31, 2016 at 05:15:53PM +, Segher Boessenkool wrote: > > If maybe_record_trace_start fails because the CFI is inconsistent on two > > paths into a block it currently just ICEs. This changes it to also d

Re: [PATCH] dwarf2cfi: Dump row differences before asserting

2016-11-10 Thread Segher Boessenkool
Ping. On Mon, Oct 31, 2016 at 05:15:53PM +, Segher Boessenkool wrote: > If maybe_record_trace_start fails because the CFI is inconsistent on two > paths into a block it currently just ICEs. This changes it to also dump > the CFI on those two paths in the dump file; debugging it without that >

Re: [PATCH] dwarf2cfi: Dump row differences before asserting

2016-10-31 Thread Kyrill Tkachov
On 31/10/16 17:15, Segher Boessenkool wrote: If maybe_record_trace_start fails because the CFI is inconsistent on two paths into a block it currently just ICEs. This changes it to also dump the CFI on those two paths in the dump file; debugging it without that information is hopeless. Tested o

[PATCH] dwarf2cfi: Dump row differences before asserting

2016-10-31 Thread Segher Boessenkool
If maybe_record_trace_start fails because the CFI is inconsistent on two paths into a block it currently just ICEs. This changes it to also dump the CFI on those two paths in the dump file; debugging it without that information is hopeless. Tested on powerpc64-linux {-m32,-m64}. Is this okay for