>> AFAIK the default for x86_64 is to omit frame pointer >> for optimized builds so you probably do not have it in most cases in VPP >> builds (but I did not check). >> So when perf tries to interpret random data as frame pointer, this is >> what you get :) >> The most reliable (but slowest) should be dwarf. lbr should be the way >> to go on Intel Haswell and later. > FWIW, this is being run on the Macchiatobin platform (i.e., aarch64 > cortex-A72). :)
My bad. Not sure what is going-on but it looks like gcc also omit fp by default on aarch64: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84521 Did you had a chance to try dwarf instead of fp? Ben
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13997): https://lists.fd.io/g/vpp-dev/message/13997 Mute This Topic: https://lists.fd.io/mt/34128898/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
