On Wed, May 10, 2017 at 10:32:06AM +0200, Jiri Slaby wrote: > > But it does hurt, in the sense that the complicated format of DWARF CFI > > means the unwinder has to jump through a lot more hoops to read it. > > Why that matters, actually? Unwinder is nothing to be performance > oriented. And if somebody is doing a lot of unwinding during runtime, > they can switch to in-this-case-faster FP unwinder.
perf (and ftrace) like the unwinder to be considered performance oriented.
